Software Engineering Term Paper

Download this Term Paper in word format (.doc)

Note: Sample below may appear distorted but all corresponding word document files contain proper formatting

Excerpt from Term Paper:

Software Engineering

Outline requirements for a Supermarket Checkout System -- The checkout system in a supermarket consists of a store computer to which the cash registers are connected. Each cash register is equipped with its own processor, a keypad with numeric keys and function keys, an electronic barcode scanner, a scale, a customer order receipt printer, a credit/debit card reader, a credit/debit card receipt printer and a display where item and price information is shown. The display is visible to both the customer and the cashier. Each register has a holder for a till containing cash, checks, coupons, etc., which is automatically opened at the end of each customer transaction. As a cashier begins a shift, he or she inserts a till into the cash register, logs onto the register and waits for approval from the system. He or she is then ready to process customer orders. A customer order can only be processed when a till has been locked in the till holder. As a customer checks out an order, the cashier enters the identification number of each item. Scanning the item over the bar-code scanner or manually from the keypad does this also. In the former case, the cashier enters the number followed by the function key ITEM-ID. Based on the number, the cash register obtains product information from the product inventory. The product information contains an item description to be displayed and printed on the receipt, as well as the price. As items are being checked through, prices and item descriptions appear on the display. The system also outputs the item description and price to the customer order receipt printer. If an item is to be credited, the cashier presses CREDIT before scanning the item or manually entering the identification number. After all the items in the order have been processed, the cashier presses the SUBTOTAL function key. The cash register computes and displays the total price including tax. The tax and the total are also printed on the receipt. The SUBTOTAL button may be pressed more than once for each order. Each time, the current subtotal and tax is displayed and printed. The TOTAL button can be pressed only once for each order. Once TOTAL has been pressed, the order cannot be changed. When the total has been computed, the till is automatically opened. After the total has been displayed, the cashier accepts payment. The payment amount is entered followed by a payment type button: CASH, CHECK, and CREDIT/DEBIT. The customer may also pay by credit card or debit card. The credit/debit card reader first scans the card. A message is then sent to the appropriate credit/debit card authorization center. The credit card request is either accepted or rejected. If accepted, an authorization code is returned. The credit card number and authorization code are printed on the receipt. Two copies of a receipt are then printed on the credit/debit card receipt printer: one for the customer; the second is signed by the customer and kept by the supermarket. If a credit / debit card is not accepted and no other payment is offered, the order is canceled. When complete payment has been received, the cash register computes the amount of change displays it and prints it on the receipt. Finally, the receipt is fed out of the printer. At this point the cashier must close the till, which is automatically locked in position until the next customer transaction has been completed. A cashier repeatedly processes customer orders until the end of his or her shift. The cashier then logs off of the cash register. The log off operation unlocks the till, which is removed by the cashier. Each customer order processed is given a transaction id. A transaction log is maintained of all transactions and a daily report is automatically prepared containing the number of items sold for each product and the total revenue for the day. This report is printed on the supermarket printer and also sent to the supermarket headquarters.

1. Produce a detailed use case diagram. Document each use case using the template that I will be sending.

2. Realize the major use cases (refer to the "Use case realization" document that I will be sending) and derive a class diagram for this system.

3. Refine the class diagram where you think it is necessary. Include the major attributes and operations in each class. Distinguish between boundary, control and entity classes. Clearly specify your rationale for the choices of classes what is their responsibility in realizing a use case, and how they cooperate to accomplish a service.

NOTE -- will email use case diagram to you directly at:

Question 2

2.1

This section attempts to outline the advantages and disadvantages of forward and reverse engineering. The term reverse engineering in manufacturing is nothing more than taking apart an object to see how it works and forward engineering is often used in contrast to reverse engineering. The purpose of forward and reverse engineering is usually to see how something works, to duplicate it, to enhance the object or simply to take a part of the object or concept and to then apply what is learned to another thing or process. These unique processes were and still are practiced throughout the corporate and manufacturing environments and from older industries. When Toyota buys a Honda they intend to disassemble it to examine how certain welds, seals, or components work so that they can either improve upon or utilize similar components or processes. From the perspective of software, reverse and forward engineering could be to reverse a computer software program's machine or object code to its original source code format. The reasons do reverse engineering could be to retrieve lost source code, to study how the program performs certain operations, to improve performance, to fix a bug or error in logic, to identify malicious content such as a virus, or to change the program from one programming language into another such as COBOL to C++.

However, in regard to UML, forward engineering is a tool that converts a diagram of a process into code and it should not be limited to pictorial depiction of diagrams. The structure of a system is defined by a diagram that can be translated into actual source code or classes and a forward engineering UML tool should bridge these steps by generating source code of the classes. Developers should be able to take this 'stub' code and fill in with actual code thus speeding up the process of creating source code. Forward engineering support by a UML tool is normally for a specific language or a set of languages. Reverse engineering is exactly the opposite of forward engineering in the sense that the UML tool loads all of the files of the application or system and then identifies the dependencies between classes. In other words, it reconstructs the entire application structure with the relationships between classes.

Some advantages and disadvantages of both reverse and forward engineering are obvious. For example, one obvious disadvantage of reverse and forward is that the interpretation is not accurate. In other words, it could easily constitute an incorrect version of the original diagram or source and thus make additional work for a developer who may assume he is working with a correct interpretation. An obvious advantage in regard to reverse and forward engineering any software, object or product is that whatever the object is, it can be diagnosed to discover better ways of fixing or using the inherent parts or processes.

2.2

This section attempts to illustrate two refactoring examples useful during design. The first is a tool to reduce coupling and the second is to use CASE tools. Because refactoring is a technique for restructuring existing bodies of code by altering internal structure but not external behavior, it is still best to reduce as many internal structural concerns in the design phase. In other words, refactoring may be a series of small transformations that preserve behavior but a series of these small changes amount to a large transformation and a significant restructuring.

The first refactoring example that could be useful during the design stage is the coupling factor with a focus on: aggregation coupling, formal parameter coupling and return-type coupling. Any software with a low coupling ratio is more manageable once in production and also help the code to be more reliable. It is important to use viable strategies to reduce coupling in Object-Oriented Designs because it is a major objective of object-oriented design work to use classes with a high level of cohesion but a low level of coupling.

UML-based class diagrams should be generated early on in the software design process. Programmers today have the luxury to utilize certain tools to help examine class diagrams such as a Coupling Analyzer Tool or CAT where input is a UML class diagram. CAT provides output counts of any aggregation coupling, formal parameter coupling, and return-type coupling evident in the overall design. A software engineer utilizes this…[continue]

Some Sources Used in Document:

"Welcome-To-UML-Web-Site!" 

Cite This Term Paper:

"Software Engineering" (2005, January 14) Retrieved December 2, 2016, from http://www.paperdue.com/essay/software-engineering-60950

"Software Engineering" 14 January 2005. Web.2 December. 2016. <http://www.paperdue.com/essay/software-engineering-60950>

"Software Engineering", 14 January 2005, Accessed.2 December. 2016, http://www.paperdue.com/essay/software-engineering-60950

Other Documents Pertaining To This Topic

  • Software Engineering

    Software Engineering Requirements Are Volatile: Design, Resource Allocation, and Lifecyles Aren't So Flexible For the majority of software development initiatives, bad requirements are a fact of life. Even when there is a high quality elicitation process, requirement change throughout the software lifecycle model. This is expected, if not desired to build a system that the customers wants and will use. But, it's difficult to change design and resource allocation once these have

  • Software Engineering What Makes it Run the

    Software Engineering: What Makes it Run The Software Engineering Online Learning Center sponsored by the Institute of Electrical and Electronic Engineers (IEEE) is a wealth of useful information for anyone interested in the disciplines this organization is committed to advancing knowledge in. Divided into webcasts, DB2 tutorials, Amazon.com and eBay tutorials, Java learning tools and Linux certification tutorials, the learning center strikes a good balance between open source and proprietary software.

  • Software Engineering What Makes it Run IBM

    Software Engineering: What Makes it Run IBM and the Institute of Electrical and Electronic Engineers (IEEE) have collaborated to create the Software Engineering Online Learning Center, a portal of educational and industry information that is very useful for any student of computer science, programming or software engineering. The intent of this paper is to evaluate this portal for its applicability and value to learning. The portal is designed around IBM-centric content

  • Software Engineering

    Management Requirements engineering process is at the very core of project success. Rather than spend huge amounts of money for reworking the whole project it is prudent and cost effective to identify and rectify the problems early in the project development life cycle. We are witnessing a paradigm shift in communication and computer technology and there is a consequent change in our business methodologies. In this automated business environment there is

  • Software Engineering Requires a Decent

    This approach brings down the costs involved, the chances of delay in product release and the gives the user an option to update their requirements in successive iterative steps (Jacobson & Rumbaugh 1999, pp. 3-13). CHAPTER 2 Oracle and Microsoft SQL Server are among the most widely used databases with a large range of features with regards to their techniques of development and deployment. Both the Oracle 10g and SQL Server

  • Knowledge Oriented Software Engineering Process in a Multi Cultural...

    Knowledge-Oriented Software Engineering Process In a Multi-Cultural Context In the peer-reviewed article Knowledge-Oriented Software Engineering Process In A Multi-Cultural Context (Jaakkola, Heimburger, Linna, 2010) the authors contend that the accelerating nature of software development leaves little time for cultural assimilation and integration of teams to an optimal level. The authors have defined the specifics of how software development is changing very rapidly due to mobile platforms, cloud computing and Software-as-a-Service (SaaS). Exacerbating

  • No Silver Bullet Essence and Accidents of Software Engineering

    Silver Bullet During the 1970's, companies had difficulty delivering software within the constraints of schedule, budget, and quality (Food for Thought, 2005). The problem grew worse over time. Many projects undertaken in the 1980's and 1990's were complete disasters, failing to deliver anything, grossly exceeding budget and schedule deadlines, and delivering poor quality. Also, during the 1980's a "software crisis" occurred in which the spending on software maintenance exceeded spending


Read Full Term Paper
Copyright 2016 . All Rights Reserved