Lets now learn on how to draw activity diagram based on the cases from the use case diagrams. This diagram is for online order information system on customer side. This diagram is for online order information system on Admin/manager side. This diagram is for online booking information system passenger side. This diagram is for onlineContinue reading “Case studies on Activity diagram (part 2)”
Category Archives: Object Oriented Analysis and Design
Continuation on Activity diagram (part 1)
ACTION STATE\ ACTIVITY STATE As elements communicate with one another within a society of objects, each element has the responsibility of appropriately reacting to the communications it receives. An action state represents processing as an element fulfills a responsibility. There are various types of action states, including simple, initial, and final action states. Simple ActionContinue reading “Continuation on Activity diagram (part 1)”
ACTIVITY DIAGRAM
Activity diagrams, depict the activities and responsibilities of elements that make up a system. Activity modeling is a specialized type of behavioral modeling concerned with modeling the activities and responsibilities of elements. Activity diagram is basically a flow chart to represent the flow from one activity to another activity. The activity can be described asContinue reading “ACTIVITY DIAGRAM”
CASE STUDIES ON USE CASE DIAGRAMS (part 3)
Use case diagram for an order information system Use case diagram for an online bus booking information system.
Continuation on Use case diagrams (part 2)
ACTORS An actor is a user or external system with which a system being modeled interacts. For example an E commerce system involves various types of users including: Customers, Database administrator, user-interface manager and system administrator These users are all actors. An actor is external to a system, interacts with the system, may be aContinue reading “Continuation on Use case diagrams (part 2)”
Continuation on Use case diagrams (part 1)
Use case: Use case represents a set of actions performed by a system for a specific goal. Component: Component describes physical part of a system. Node: A node can be defined as a physical element that exists at run time. Behavioral things: A behavioral thing consists of the dynamic parts of UML models. Following areContinue reading “Continuation on Use case diagrams (part 1)”
USE CASE DIAGRAMS
Use case diagram is used to capture the dynamic nature of a system. It consists of use cases, actors and their relationships. Use case diagram is used at a high level design to capture the requirements of a system. To model a system, the most important aspect is to capture the dynamic behavior. The dynamicContinue reading “USE CASE DIAGRAMS”
INTRODUCTION TO UML
UML is a languageused for object-oriented analysis and design. UML stands for unified modelling language UML includes a set of graphical notation techniques to create visual models of software systems. Three developers of UML are Grady Booch, Ivar Jacobson and James Rumbaugh. UML is a language for visualizing, specifying, constructing, documenting. UML is not aContinue reading “INTRODUCTION TO UML”
UNIFIED PROCESS MODEL
Iterative and Incremental: The Unified Process is an iterative and incremental development process. The Elaboration, Construction and Transition phases are divided into a series of time boxed iterations. Each iteration results in an increment, which results in improved functionality. Use Case Driven: In the Unified Process, use cases are used to capture the functional requirementsContinue reading “UNIFIED PROCESS MODEL”
OBJECT-ORIENTED SOFTWARE ENGINEERING LIFE CYCLE
The following are the stages for the object-oriented software engineering life cycle Requirements Engineering: which is comprised of requirements gathering and object oriented analysis and specification OO Design: At this stage the analyst will conduct the following architectural design, detailed design, which both require the transformation of functional requirements into OO design elements Implementation orContinue reading “OBJECT-ORIENTED SOFTWARE ENGINEERING LIFE CYCLE”
