Ooad lab manual(original)


Published on

this project done in microsoft visio.

Published in: Education, Technology, Business
1 Comment
  • conference mangement system ooad new implementation there
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Ooad lab manual(original)

  2. 2. DR.JIVRAJMEHTAINSTITUTE OF TECHNOLOGY MOGAR,ANAND(GUJARAT) CERTIFICATEThis is to certify that Mr. PATEL DEEPENKUMAR VITTHALBHAI(EnrollmentNo.100820131024), student of Department ofComputer Science& Engineering (Sem:04)has successfully completed the term work ofOBJECT ORIENTED ANALYSIS AND DESIGN (140703).Remarks:Date:
  3. 3. INDEXNameof Student:PATEL DEEPENKUMAR V.EnrollmentNo.:100820131024Subject: Object Oriented Analysis and Design (140703) Date ofSr. 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. 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. 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 aninformation system, training, and user (stakeholder) ownership. AnySDLC should result in a high quality system that meets or exceedscustomer expectations, reaches completion within time and costestimates, works effectively and efficiently in the current and plannedInformation Technology infrastructure, and is inexpensive to maintainand cost-effective to enhance.[2] Computer systems are complex andoften (especially with the recent rise of service-oriented architecture)link multiple traditional systems potentially supplied by different softwarevendors. To manage this level of complexity, a number of SDLC modelsor methodologies have been created, such as "waterfall"; "spiral"; "Agilesoftware development"; "rapid prototyping"; "incremental"; and
  6. 6. "synchronize and stabilizeSDLC models can be described along spectrum of agile to iterative tosequential. Agile methodologies, such as XP and Scrum, focus onlightweight processes which allow for rapid changes along thedevelopment cycle. Iterative methodologies, such as Rational UnifiedProcess and dynamic systems development method, focus on limitedproject scope and expanding or improving products by multipleiterations. Sequential or big-design-up-front (BDUF) models, such asWaterfall, focus on complete and correct planning to guide largeprojects and risks to successful and predictable results[citation needed].Other models, such as Anamorphic Development, tend to focus on aform of development that is guided by project scope and adaptiveiterations of feature development.In project management a project can be defined both with a project lifecycle (PLC) and an SDLC, during which slightly different activitiesoccur. According to Taylor (2004) "the project life cycle encompassesall the activities of the project, while the systems development life cyclefocuses on realizing the product requirements".[4] SDLC (systemsdevelopment life cycle) is used during the development of an IT project,it describes the different stages involved in the project from the drawingboard, 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 organizations 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 organizations 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. 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 softwares life: changes, correction, additions, moves to a different computing platform and more. This is often the longest of the stages.System analysisThe goal of system analysis is to determine where the problem is in anattempt to fix the system. This step involves breaking down the systemin different pieces to analyze the situation, analyzing project goals,breaking down what needs to be created and attempting to engageusers so that definite requirements can be defined.DesignIn systems design the design functions and operations are described indetail, including screen layouts, business rules, process diagrams andother documentation. The output of this stage will describe the newsystem as a collection of modules or subsystems.The design stage takes as its initial input the requirements identified inthe approved requirements document. For each requirement, a set of
  8. 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, andgenerally include functional hierarchy diagrams, screen layoutdiagrams, tables of business rules, business process diagrams,pseudocode, and a complete entity-relationship diagram with a full datadictionary. These design elements are intended to describe thesoftware in sufficient detail that skilled programmers may develop thesoftware with minimal additional input design.TestingThe code is tested at various levels in software testing. Unit, systemand user acceptance testings are often performed. This is a grey areaas many different opinions exist as to what the stages of testing are andhow much, if any iteration occurs. Iteration is not generally part of thewaterfall model, but usually some occur at this stage. In the testing thewhole system is test one by oneFollowing 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. 9. 03. System Requirement SpecificationAim: To Study the System Requirement Specification of the Project Selected.Required Tools: NoneProcedure: 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. 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 PersonGeneralization:- 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. 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 users 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 DIAGRAMINTERACTION 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 – Objects existence during the interaction.
  12. 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 2Object:- 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. 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. 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
  16. 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 * -End8Actor1 * UseCase4 -End11 * * <<include>> -End10 <<extend>> -End13 -End14 UseCase5 * * * Actor2 <<include>> -End12 <<extend>> -End16 * -End15 UseCase6 * * Actor3
  17. 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 -NAMETop 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. 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. 19. 08.State Diagrams and ActivityDiagramsAim: To perform the behavioral view diagram.Required Tools: Microsoft Visio /Visual Paradigm/Netbeans6.XProcedure: 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. 20. ACTIVITY DIAGRAM testing -End4 * [if failed] -End3 * [if passed] training & adventure -End2 * [over age limit & corruption] [under age limit] mission civil services * -End1