1. Prepared by Afra`a Sayah

2. Introduction. Weekly Tasks. Plane Phase. Analysis Phase. Design Phase. Report Rules. Conclusion. 2

3.  Learn the software development life cycle (project management, requirements engineering, systems modeling, software design, prototyping, and testing).  Perform the software phases by developing a complete and consist software.  Learn how to work in a team and develop leadership skills.  Learn the UML for visual modeling. 3

4. In this course Lab you will perform the software development life cycle by creating a project in a team work environment and use the UML for analyzing and designing your project. you will go through three phases: 1. Plane Phase. 2. Analysis Phase. 3. Design Phase. 4

5. 1. Weekly Report. Weekly Report# NameFinish DateStart DateTaskID 5

6. 2. Meeting Report: Meeting No#... Report Date: Time: Team Name: Absent:  Task to be achieved :  Done tasks:  Task that we could not achieved this week: 6

7. 1. Description: Define the place or the activity that your system will work on, the problem that it face and the solutions and new activity that your system will provide generally. 7

8. 2. Problem Statement. Identify all problems that led you to develop your system. 3. Benefits of the System. Describe the solutions that the system provides or the new functions that it adds. 4. Solution Methodology. 8

9. We are going to use the waterfall model which is a system development life cycle model that uses a linear and sequential approach. This model contain five phases as following: 9

10. 4. Solution Methodology. 10

11. 5. Environment: Indorse or outdoors. 11

12. 5. Requirements Analysis: Requirements analysis is critical to the success of a software development. Requirements must be actionable, measurable, testable, clear and meets the needs or constrains, and defined to a level of detail sufficient for system design. 12

13. 1.Identifaying Stakeholders: Stakeholders: Any person who has an interest (direct or indirect) in the project. A stakeholder is not necessarily an actor. But an actor is usually a stakeholder. 13

14. 2. Elicit Requirements: 1. Interviewing:  Avoid misleading questions.  Keep questions short and precise.  Check that questions are understood. 14

15. 2. Elicit Requirements: 2. Questioner: You will ask about  Context and background.  Current system or operations.  Problems and limitations in the current system.  Requirements for a new system, improvement, new functions etc. 15

16. 3. Requirement Gathering: Document all the system functions that you have generate from the electing requirement stage. 16

17. 4. Define the Types of Requirements: 1.Functional Requirements: What the system should do. 2. Non Functional Requirements: Properties and constrains the system should acquire. 17

18. Non Functional Requirements: You will study them from the fallowing views:  Business Goals View.  Security View.  Accessibility and Look-and-Feel View.  Efficiency View.  The Interface Metaphor or Analogy.  Interface Structure Design. 18

20. The analysis phase is where we show how the system will operates by dividing it into component and understand each one and how they interact with each other. 20

21. Entity Relationship Diagram(ERD): Representing the objects and their relationships in the data model for a software product. Entity Relationship Diagram Elements: 1. Identify Entity 2. Find Relationship 21

22. Entity Relationship Diagram(ERD): 3. Define Primary Key: Identify attribute(s) that uniquely identify each entity. 4. Identify Attributes: Component of the entity. 5. Determine the Cardinality: ID Ph ID 22

23. UML Diagrams: Unified Modeling Language (UML) is a standardized general-purpose modeling language. It `s capture the structure and behavior of the system components, show how the elements of the system interact together in an unambiguous way and it`s gives consistency between a design and its implementation. 23

24. UML Diagrams: Consists of:  Use Case Diagram.  Class Diagram.  Interaction Diagrams  Sequence Diagram.  Collaboration Diagram.  Object Diagram. 24

25. 1.Use Case Diagram. It document the behavior of the system by giving graphical overview of its functions (use cases), surroundings (actors), and relationships between the use cases and actors (use case diagrams). Add Course 25

26. 1. Use Case Diagram. A use-case consist of four component which are: 1.Actors:  A person, organization, that interact with our system.  Represented in UML as a stickman. 26

27. 1. Use Case Diagram. 2. Use Case:  Describes a set of sequences of actions that the system performers to give a value to an actor.  Represented in UML as an ellipse. 27

28. 1. Use Case Diagram. 3. Association:  Is a relationship between an actor and a use case.  Represented in UML as an arrow that indicates who initiates the relationship. 28

29. 1. Use Case Diagram. 3. Name:  Describes the use case diagram. Add Course 29

30. 2. Class Diagram: Represent the object (entities) of the system in form of class. A class contains three parts which are: 1.Class Name. 2.Attributes. 3.Operations. Attributes Class Name Operations 30

31. 3. Interaction Diagram: 1.Sequence Diagram: A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram that shows how processes operate with one another and in what order. It is a construct of a message sequence chart. Sequence diagrams are sometimes called event diagrams, event scenarios, and timing diagrams. 31

32. 3. Interaction Diagram: It is composed of a diagram that contains: 1 ) Name. 2) Participating object in the form of lifeline composed of:  A rectangle representing the participating object.  A dotted line that extends for the time period of the interaction. 3) Messages to communicate among the participating object. Give ID PatientRegisterDB Give ID Enter ID 32

33. The message arrows represent the communications between two objects in a sequence diagram. It goes from the lifeline of one object to that of another object.  Synchronous message where the sending object suspends action and waits for the response to the message.  Asynchronous message where the sending object continues with its operations without waiting for the response. (Filled Head) (Open Head) 33

34. Diagram of Deleting an Appointment: 34

35. Diagram of the Distribution of the Annual Budget: 35

36. Diagram of the Distribution of the Additional Money: 36

37. Diagram of Sending Letters: 37

38. 3. Interaction Diagram: 2.Collaboration Diagram:  Collaboration diagrams belong to a group of UML diagrams called interaction diagrams. Collaboration diagrams, like sequence diagrams, show how objects interact over the course of time. However, instead of showing the sequence of events by the layout on the diagram, collaboration diagrams show the sequence by numbering the messages on the diagram. 38

39. 3. Interaction Diagram: 2.Collaboration Diagram:  This makes it easier to show how the objects are linked together, but harder to see the sequence at a glance.  You can develop a collaboration diagram in IBM Rational rose by selecting a sequence and then click on F5. 39

40. Data Flow Diagram :  A data flow data diagram demonstrate the functional model of a software product. DFDs do not represent program logic like flowcharts do. 40

41. Data Flow Diagram : Context Level DFD: 41 0.0 Lemonade System EMPLOYEECUSTOMER Pay Payment Order VENDOR Payment Purchase Order Production Schedule Received Goods Time Worked Sales Forecast Product Served

42. Data Flow Diagram : Level 0 DFD: 42 2.0 Production EMPLOYEE Production Schedule 1.0 Sale 3.0 Procure- ment Sales Forecast Product Ordered CUSTOMER Pay Payment Customer Order VENDOR Payment Purchase Order Order Decisions Received Goods Time Worked Inventory Product Served 4.0 Payroll

43. AfraaSayah12@hotmail.com 43

44. 44