![2012 - 13
OBJECTORIENTEDANALYSISANDDESIGN
(O.O.A.D) SUBJECT
CODE:140703
DEPARTMENT OF COMPUTER SCIENCE & ENGG
DR. JIVRAJMEHTA INSTITUTE OF TECHNOLOGY
MOGAR,ANAND
[LAB MANUAL]
COMPUTERSCIENCE & ENGINEERING–SEMESTER04](https://image.slidesharecdn.com/ooadlabmanualoriginal-120729112330-phpapp02/85/Ooad-lab-manual-original-1-320.jpg)
![02 .Phases in Software Development
Aim: Phases in software development project, overview, need, coverage of topics
Required Tools: None
Procedure:
1. Study different Software Development Life Cycles using your resources and
describe each phase briefly.
2. You can take help of different book sand online resources available on
internet.
The SDLC is a process used by a systems analyst to develop an
information system, training, and user (stakeholder) ownership. Any
SDLC should result in a high quality system that meets or exceeds
customer expectations, reaches completion within time and cost
estimates, works effectively and efficiently in the current and planned
Information Technology infrastructure, and is inexpensive to maintain
and cost-effective to enhance.[2] Computer systems are complex and
often (especially with the recent rise of service-oriented architecture)
link multiple traditional systems potentially supplied by different software
vendors. To manage this level of complexity, a number of SDLC models
or methodologies have been created, such as "waterfall"; "spiral"; "Agile
software development"; "rapid prototyping"; "incremental"; and](https://image.slidesharecdn.com/ooadlabmanualoriginal-120729112330-phpapp02/85/Ooad-lab-manual-original-5-320.jpg)
!["synchronize and stabilize
SDLC models can be described along spectrum of agile to iterative to
sequential. Agile methodologies, such as XP and Scrum, focus on
lightweight processes which allow for rapid changes along the
development cycle. Iterative methodologies, such as Rational Unified
Process and dynamic systems development method, focus on limited
project scope and expanding or improving products by multiple
iterations. Sequential or big-design-up-front (BDUF) models, such as
Waterfall, focus on complete and correct planning to guide large
projects and risks to successful and predictable results[citation needed].
Other models, such as Anamorphic Development, tend to focus on a
form of development that is guided by project scope and adaptive
iterations of feature development.
In project management a project can be defined both with a project life
cycle (PLC) and an SDLC, during which slightly different activities
occur. According to Taylor (2004) "the project life cycle encompasses
all the activities of the project, while the systems development life cycle
focuses on realizing the product requirements".[4] SDLC (systems
development life cycle) is used during the development of an IT project,
it describes the different stages involved in the project from the drawing
board, through the completion of the project.
Systems development phases
Preliminary analysis: The objective of phase1 is to conduct a
preliminary analysis, propose alternative solutions, describe costs
and benefits and submit a preliminary plan with
recommendations.
Conduct the preliminary analysis: in this step, you need to find out
the organization's objectives and the nature and scope of the
problem under study. Even if a problem refers only to a small
segment of the organization itself then you need find out what the
objectives of the organization itself are. Then you need to see
how the problem being studied fits in with them.
Propose alternative solutions: In digging into the organization's
objectives and specific problems, you may have already covered
some solutions. Alternate proposals may come from interviewing
employees, clients , suppliers, and/or consultants. You can also
study what competitors are doing. With this data, you will have](https://image.slidesharecdn.com/ooadlabmanualoriginal-120729112330-phpapp02/85/Ooad-lab-manual-original-6-320.jpg)
![ACTIVITY DIAGRAM
testing
-End4 *
[if failed]
-End3
*
[if passed]
training & adventure
-End2 *
[over age limit &
corruption]
[under age limit]
mission civil services
* -End1](https://image.slidesharecdn.com/ooadlabmanualoriginal-120729112330-phpapp02/85/Ooad-lab-manual-original-20-320.jpg)
Ooad lab manual(original)
- 1. 2012 - 13 OBJECTORIENTEDANALYSISANDDESIGN (O.O.A.D) SUBJECT CODE:140703 DEPARTMENT OF COMPUTER SCIENCE & ENGG DR. JIVRAJMEHTA INSTITUTE OF TECHNOLOGY MOGAR,ANAND [LAB MANUAL] COMPUTERSCIENCE & ENGINEERING–SEMESTER04
- 2. DR.JIVRAJMEHTAINSTITUTE OF TECHNOLOGY MOGAR,ANAND(GUJARAT) CERTIFICATE This is to certify that Mr. PATEL DEEPENKUMAR VITTHALBHAI (EnrollmentNo.100820131024), student of Department of Computer Science& Engineering (Sem:04)has successfully completed the term work of OBJECT ORIENTED ANALYSIS AND DESIGN (140703). Remarks: Date:
- 3. INDEX Nameof Student:PATEL DEEPENKUMAR V. EnrollmentNo.:100820131024 Subject: Object Oriented Analysis and Design (140703) Date of Sr. No. Name of the Topic Page no. Signature Submission 01. Team Information Phases in software development project, 02. overview, need, coverage of topics 03. System Requirement Specification DFD: To perform the function oriented 04. diagram Use case diagram :Toper form the 05. user’s view analysis Class diagram, Object diagram: To 06. draw the structural view diagram Sequence diagram, Collaboration 07. diagram: To draw the behavioral view diagram State-chart diagram, Activity diagram: 08. To draw the behavioral view diagram 09. Conclusion
- 4. 01. Team Information Name of the Project: ARMY MANAGEMENT SYSTEM No. of Team Members: 3 Name of Team Members: o PATEL DEEPENKUMAR V. o PRAJAPATI ANKIT H. o UPADHYAY GUNANAK R. Name of Team Leader: PATEL DEEPENKUMAR V.
- 5. 02 .Phases in Software Development Aim: Phases in software development project, overview, need, coverage of topics Required Tools: None Procedure: 1. Study different Software Development Life Cycles using your resources and describe each phase briefly. 2. You can take help of different book sand online resources available on internet. The SDLC is a process used by a systems analyst to develop an information system, training, and user (stakeholder) ownership. Any SDLC should result in a high quality system that meets or exceeds customer expectations, reaches completion within time and cost estimates, works effectively and efficiently in the current and planned Information Technology infrastructure, and is inexpensive to maintain and cost-effective to enhance.[2] Computer systems are complex and often (especially with the recent rise of service-oriented architecture) link multiple traditional systems potentially supplied by different software vendors. To manage this level of complexity, a number of SDLC models or methodologies have been created, such as "waterfall"; "spiral"; "Agile software development"; "rapid prototyping"; "incremental"; and
- 6. "synchronize and stabilize SDLC models can be described along spectrum of agile to iterative to sequential. Agile methodologies, such as XP and Scrum, focus on lightweight processes which allow for rapid changes along the development cycle. Iterative methodologies, such as Rational Unified Process and dynamic systems development method, focus on limited project scope and expanding or improving products by multiple iterations. Sequential or big-design-up-front (BDUF) models, such as Waterfall, focus on complete and correct planning to guide large projects and risks to successful and predictable results[citation needed]. Other models, such as Anamorphic Development, tend to focus on a form of development that is guided by project scope and adaptive iterations of feature development. In project management a project can be defined both with a project life cycle (PLC) and an SDLC, during which slightly different activities occur. According to Taylor (2004) "the project life cycle encompasses all the activities of the project, while the systems development life cycle focuses on realizing the product requirements".[4] SDLC (systems development life cycle) is used during the development of an IT project, it describes the different stages involved in the project from the drawing board, through the completion of the project. Systems development phases Preliminary analysis: The objective of phase1 is to conduct a preliminary analysis, propose alternative solutions, describe costs and benefits and submit a preliminary plan with recommendations. Conduct the preliminary analysis: in this step, you need to find out the organization's objectives and the nature and scope of the problem under study. Even if a problem refers only to a small segment of the organization itself then you need find out what the objectives of the organization itself are. Then you need to see how the problem being studied fits in with them. Propose alternative solutions: In digging into the organization's objectives and specific problems, you may have already covered some solutions. Alternate proposals may come from interviewing employees, clients , suppliers, and/or consultants. You can also study what competitors are doing. With this data, you will have
- 7. three choices: leave the system as is, improve it, or develop a new system. Describe the costs and benefits. Systems analysis, requirements definition: Defines project goals into defined functions and operation of the intended application. Analyzes end-user information needs. Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation. Development: The real code is written here. Integration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability. Acceptance, installation, deployment: The final stage of initial development, where the software is put into production and runs actual business. Maintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This is often the longest of the stages. System analysis The goal of system analysis is to determine where the problem is in an attempt to fix the system. This step involves breaking down the system in different pieces to analyze the situation, analyzing project goals, breaking down what needs to be created and attempting to engage users so that definite requirements can be defined. Design In systems design the design functions and operations are described in detail, including screen layouts, business rules, process diagrams and other documentation. The output of this stage will describe the new system as a collection of modules or subsystems. The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of
- 8. one or more design elements will be produced as a result of interviews, workshops, and/or prototype efforts. Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudocode, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input design. Testing The code is tested at various levels in software testing. Unit, system and user acceptance testings are often performed. This is a grey area as many different opinions exist as to what the stages of testing are and how much, if any iteration occurs. Iteration is not generally part of the waterfall model, but usually some occur at this stage. In the testing the whole system is test one by one Following are the types of testing: Defect testing the failed scenarios, including defect tracking Path testing Data set testing Unit testing System testing Integration testing Black-box testing White-box testing Regression testing Automation testing User acceptance testing Performance testing
- 9. 03. System Requirement Specification Aim: To Study the System Requirement Specification of the Project Selected. Required Tools: None Procedure: 1. Different Team members to be assigned the module to study different tasks of the system. You may take help of your faculty advisor. 2.You can meet there a world users of the same system. 3.There would be session of presentation of the analyzed system on a predefined date allotted by the faculty advisor. 4.Describe briefly, each and every specification below. UML NOTATION Unified Modeling Language. Set of notations and conventions used to describe and model an application. Universal language for modeling systems. Standard notation for OO modeling systems. Does not specify methodology to develop an application. UML DIAGRAMS Class Diagram Use Case Diagram Behavioral Diagram Interaction Diagram Sequence Diagram Collaboration Diagram State Chart Diagram Activity Diagram CLASS DIAGRAM Shows the static structure of the model. Collection of static modeling elements such as classes and their relationships connected as a graph. Provides visual representation of objects, relationships and their structures.
- 10. Class:- A class is a set of objects that share a common structure and common behavior. It is represented as: <Class Name> <Attributes> <Operations> Interface:- Specifies the externally-visible operations of a class and/or component. Association:- Model properties of associations. The properties are stored in a class and linked to the association relationship. Example, Bank Account Person Generalization:- A generalize relationship is a relationship between a more general class or use case and a more specific class or use case. Example, Vehicle Bus Truck Car
- 11. USE CASE DIAGRAM Set of use cases enclosed by system boundary, communication association between actors and use cases, and generalization among use cases. Actors:- External factors that interacts with the system from the user's perspective. Use Cases:- Set of scenarios that describe how actor uses the system. Represented as, Relationship:- Communication – communications with the use case normally. Uses – Shown by generalization arrow from the use cases. Extends – Used when one case does more than another that is similar to it. BEHAVIOR DIAGRAM INTERACTION DIAGRAM Diagrams that describes how group of objects are collaborated. SEQUENCE DIAGRAM: Describes the behavior of the system through interaction between the system and the environment in time sequence. Two dimensions: Vertical dimension – represents time. Horizontal dimension – represents objects. Life line – Object's existence during the interaction.
- 12. Object 1 Object 2 <Event> COLLABORATION DIAGRAM: An interaction diagram that shows the order of messages that implement an operation or a transaction. Collaboration diagrams show objects, their links, and their messages. Object 1 1. <Event > Object 2 Object:- An object has state, behavior, and identity. Objects interact through their links to other objects. Link:- A link is an instance of an association, analogous to an object. Message:- A message is the communication carried between two objects that trigger an event. STATECHART DIAGRAM Models the dynamic behavior of individual classes or any other kind of object. Shows the sequences of states, events, and actions. State:- Represents a condition or situation during the life of an object during which it satisfies some condition or waits for some event. <State>
- 13. Start State:- Shows the beginning of workflow. End state::- Represents the final or terminal state. ACTIVITY DIAGRAM Used for modeling the sequence of activities in a process Special case of a state machine in which most of the states are activities and most of the transitions are implicitly triggered by completion of the actions in the source activities. Activity:- Represents the performance of task or duty in a workflow. <Activity> Swim lanes:- Represents organizational units or roles within a business model.
- 14. 04.Data Flow Diagrams Aim: To perform the function oriented program using Data Flow Diagram. Required Tools: Microsoft Visio /Visual Paradigm/Netbeans6.X Procedure: 01.Trace various data, processes, input, output etc. of the system and analyze the same. 02.Use processes at various levels to draws the DFDs. DFD AT LEVEL 0 Sortied candidate candidate training Apply weapon If selected testing Send request Enquiry for supply Training & Supplier for adventure weapon vendor Civil health Doctors services mission services vehicles mission vehicle
- 15. DFD AT LEVEL 1 CANDIDATE WEAPON VEHICLE WRITTEN TEST VENDOR VENDOR WEAPON ORDER IF NEED VEHICLE ORDER IF NEED WEAPON VEHICLE PHYSICAL TEST WEAPON VEHICLE SUPPLIER SUPPLIER IF PASSED ENQUIRY TO USE WEAPON ENQUIRY TO USE VEHICLE SORTED TRAINING & CANDIDATE ADVENTURE FOOD MISSION COOK MISSION HEALTH CIVIL SERVICES DOCTOR SERVICES
- 16. 05.UseCase Diagrams Aim: To perform the user’s view analysis. Required Tools: Microsoft Visio /Visual Paradigm/Netbeans6.X Procedure: 01.Tracevarious processes, use-cases, actors etc. of the system and analyze. 02.Use processes at various levels to draws the Use Case Diagrams. System -End2 UseCase1 * -End4 UseCase2 * -End1 -End3 -End6 * -End5 UseCase3 * -End7 * * -End9 * -End8 Actor1 * UseCase4 -End11 * * <<include>> -End10 <<extend>> -End13 -End14 UseCase5 * * * Actor2 <<include>> -End12 <<extend>> -End16 * -End15 UseCase6 * * Actor3
- 17. 06.Class Diagrams and Object Diagrams Aim :To perform the structural view diagram. Required Tools: Microsoft Visio /Visual Paradigm/Netbeans6.X Procedure: 01.Trace various elements such as classes, member variables, member functions etc. of the class diagram. 02.Draw class diagram as per the analysis done by you. 03.Identify various elements such as various objects of the object diagram. 04.Draw object diagram as per the analysis done by you. Top Package::VEHICLE Top Package::WEAPON -NAME Top Package::TESTING -NAME -QTY. -QTY. -SUPPLY -CANDIDATE -IN STOCK -BUY -SORT LIST -SUPPLY +BUY() +PHYSICAL TEST() +BUY () * +SUPPLY() +WRITTEN TEST() +SUPPLY() *... -End1 -End5 1... * 1... -End3 * * -End4 * -End2 *... *... ...1* -End6 Top Package::TRAINNING & ADVENTURE -OFFICERS -CANDIDATE * -End13 -TRAINERS *... *... +TRAINIG() -End7 * *... * -End9 * *... -End11 -End14 * *... *... Top Package::HEALTH * Top Package::FOOD-End8 -NAME -DETAILS -COOK +CHECKING() +COOKING FOOD() -End12 +OPERATION() * *... * -End10 *... Top Package::CIVIL SERVICES -NAME Top Package::MISSION -LOCATION -NAME -MEMBERS -LOCATION -PEOPLE SAVED -MEMBERS +COUNTING PEOPLE IN DIE() +() +COUNTING PEOPLE IN SAVED()
- 18. 07.Sequence Diagrams and Collaboration Diagrams Aim: To perform the behavioral view diagram. Required Tools: Microsoft Visio /Visual Paradigm/Netbeans6.X Procedure: 01.Trace various elements such as controller classes, objects, boundaries, messages etc. of the sequence diagram. 02.Draw sequence diagrams per the analysis done by you. 03.Identify various elements such as various objects of the collaboration diagram. 04.Draw collaboration diagram as per the analysis done by you. ARMY MANAGEMENT SYSTEM :CANDIDATE :FORM COLLECTING :TESTING :TRAINING & ADVENTURE :MISSION :CIVIL SERVICES APPLY TO JOIN GO FOR TESTING IF FAILED IF PASSED IF NEED GO FOR APPLY AFTER COMPLETION IF NEED AFTER COMPLETION LEAVE
- 19. 08.State Diagrams and ActivityDiagrams Aim: To perform the behavioral view diagram. Required Tools: Microsoft Visio /Visual Paradigm/Netbeans6.X Procedure: 01.Identify various elements states and their different transition of the state-chart diagram. 02.Draw state diagram as per the analysis done by you. 03.Identify various elements such as different activity their boundaries etc. of the activity diagram. 04.Draw Activity diagrams per the analysis done by you. STATE DIAGRAM ready If failed testing If passed Training Above age limit & adventure If needed If needed corruption Civil mission services After complition
- 20. ACTIVITY DIAGRAM testing -End4 * [if failed] -End3 * [if passed] training & adventure -End2 * [over age limit & corruption] [under age limit] mission civil services * -End1