Object orientate application development II (III)
eadariq.seais
yourname_ITSD424_IP11.docx
Course Number
Course Section
Course Name
Project Name (Unit 1 IP)
Student Name
Table of Contents Table of figures 2 Introduction 3 Use cases 4 Class Diagram 4 Activity diagram 5 Sequence diagram 7 Phase 2 Application Screenshots 8 References 11
Table of figures
Figure 1: Online order system use case diagram 4
Figure 4: Sequence diagram 7
Figure 6: Address entry screen 9
Figure 7: Customer information Screen 9
Figure 8: Order menu before order is placed 10
Figure 9: Order menu after order is placed 11
UML Model for Project
Introduction
System design is a process that helps to conceptualize the software system requirements into a software implementation. It involves taking the user requirements and using it to define system architecture, interfaces and modules for the system. The most widely used method for software system design today is Object-Oriented analysis and design methods for their reusability and easy way of expressing relationship between system components(Martin, 2011). To be able to efficiently utilize the power of object-oriented analysis and design methods you need to use its standard language, Unified Modeling language (UML). UML is a general purpose modeling language that is used to provide a standard way to visualize the design of a system. UML is rich of modeling notations and methods that are used to create different diagrams to represent structural and behavior information of the system (Wazlawick, 2014). Example of this diagrams include class diagram, use case diagram, deployment diagrams, activity diagram, state, object, and sequence among other.
The diagram in the following sections represents the structural and behavior of the Online ordering system.
Use cases
Use case diagram are used to represent a user’s interaction with the system hence showing the relationship between the system and its users. Use cases identify the different actors (users) of the system and the different ways (use cases) they interact with the system. The use case diagram below shows the two main users of the online orders system and how the use the system.
Figure 1: Online order system use case diagram
Class Diagram
UML Class diagram are static structure diagram used to describe the structure of software system by showing classes, operations, their attributes and the relationship among them. Classes form the main building block of Object Oriented modeling and hence class diagram help to conceptualize the general structure of the system that can later be translate into programming code. Classes in class diagram represent the main elements in the application to be programmed (Booch, 1994).
The diagram below show the class diagram for the recommend online ordering system. Boxes represent classes. Boxes are supposed to have three compartments to complete the represent class information in full, one for class name, second for class attributes and the third for class operations. The diagram below shows a simple representation of classes. The lines represent links between classes and show the kind of relationship between classes. For example user is generalization for customer and sales. Customer makes order, and order is composed of products
Activity diagram
Activity diagram are used to show the order in which actions take place in the system and their outcomes. Activity diagram are used by system analyst are modeling tools so as to help understand how objects in the system behave and interact with the system(Alan Dennis, Barbara Haley Wixom, 2012). Activity can be used to represent single or multiple use cases. The diagram below show the events taking place in the system from the time customer logs in into the system to the time the time they logout.
Sequence diagram
Sequence diagram is used to describe how interaction within the system objects. The sequence diagram illustrates the Classes and object involved in the interaction scenario and the sequence of exchange of messages between the objects(Gary B. Shelly, 2012). Sequence diagrams focus on the ‘lifelines’ of an object and the communication with other objects in carrying out the functions before the end of their lifelines.
The sequence diagram below shows interaction of the two objects with the system. The objects involved in the collaboration are displayed by boxes at the top of the diagram.
Phase 2 Application Screenshots
Figure 6: Address entry screen
Figure 7: Customer information Screen
Figure 8: Order menu before order is placed
Figure 9: Order menu after order is placed
References Alan Dennis, Barbara Haley Wixom, R. (2012). System Analysis and Design (5th Editio ed.). Danver: John Wiley & Sons, Inc. Booch, G. (1994). Object Oriented Analysis and Design with Applications. Oghenekaro, P., & C, E. (2008). A Comparative Analysis of Structured and Object-Oriented Programming Methods. (c). Wazlawick, R. (2014). Object-Oriented Analysis and Design for Information Systems. Object-Oriented Analysis and Design for Information Systems .
12 | Page
