System Analysis Course

Get Started. It's Free
or sign up with your email address
Rocket clouds
System Analysis Course by Mind Map: System Analysis Course

1. Lecture 06: UML 1.5 :Unified Modeling Language

1.1. UML Diagrams :OOP Technic

1.1.1. Structured Diagrams

1.1.1.1. Class Diag.

1.1.1.1.1. Consists of

1.1.1.1.2. Diag. Relations

1.1.1.2. UseCase Diag. :show which actors participate in each use case

1.1.1.3. Physical view

1.1.1.3.1. Component Diag.

1.1.1.3.2. Deployment Diag.

1.1.2. Dynamic Diagrams

1.1.2.1. State Diag.

1.1.2.2. Activity Diag. :sequential and concurrent groups of activities

1.1.2.3. Interaction View

1.1.2.3.1. Sequence Diag. :Shows the behavior sequence of use case.

1.1.2.3.2. Collaboration Diag. :shows the relationship among roles

1.2. Model Management

1.2.1. Package :A set of packages that hold model elements, such as classes, state machines, and use cases.

1.2.2. Extensibility constructs

1.2.2.1. Constraint (XOR)

1.2.2.2. StereoType & Icon (DB Icon)

1.2.2.3. Tagged Values (Name=Ahmed)

2. Lecture 05: Use Case :Requirement specification

2.1. Use-Case Diageam consists of:

2.1.1. Actors: Who are the System-Users

2.1.1.1. Role

2.1.1.1.1. Employee

2.1.1.1.2. Customer

2.1.1.1.3. Guest

2.1.1.2. Organization

2.1.1.3. Device

2.1.1.4. System

2.1.2. Scope: System border

2.1.3. Use-Cases: What they will do with the system

2.1.4. Relations between Actors & Use-Cases

2.1.4.1. Association

2.1.4.2. Multiplicity

2.1.4.3. Generalization (Inheritance) :similar objects are combined in a Superclass

2.1.4.4. Specialization (Realization) :subclasses are created from an existing Superclass

2.1.5. Relation between Use-Cases

2.1.5.1. Extend :conditionally adds steps

2.1.5.2. Include :is used to extract use case

2.2. Specifying System Behavior Problems

2.2.1. The implicit scope

2.2.2. Too little (or too much) definition

2.2.3. Ambiguities and contradictions

2.2.4. Over or missing specification

2.2.5. Focus on the wrong aspects: internals, user interface, design constraints

2.3. Purpose of Use Cases

2.3.1. Define the scope

2.3.2. structure to the requirements

2.3.3. unambiguous statement

2.3.4. capture vocabulary

2.3.5. example interactions

2.3.6. guide the design phase

2.3.7. validate the class model

2.3.8. precise system requirements

2.3.9. all stakeholders can comprehend

2.3.10. basis of the user manuals and test cases for the system

2.4. Lecture Notes

2.4.1. Martin Fowler a software engineer, specializing in object-oriented analysis and design, UML, agile software development methodologies, extreme programming.

2.4.2. A Use Case System Diagram may consist of 12 Cases only.

2.4.3. Authentication: Who is the user? Authorization: What you can do?

2.4.4. Stereo-Type :Classifier for a classifier

2.4.5. Name use cases with verb phrases

3. Lecture 03: How to Gather the requirements?

3.1. Gathering requirements techniques:

3.1.1. Interview

3.1.1.1. Open interviews

3.1.1.2. Closed interviews

3.1.1.3. Semi-closed interviews

3.1.2. users groups

3.1.3. survey

3.1.3.1. questionnaire

3.1.3.2. random sample

3.1.3.3. direct random sample

3.1.3.4. direct sample

3.1.3.5. used closed questions

3.1.4. observation

3.1.4.1. Physical‬‬

3.1.4.2. Automated

3.1.5. Shadow

3.1.5.1. No interactions should be made

3.1.6. User structure

3.2. Personal Skills

3.2.1. Analyst

3.2.1.1. Enough experience

3.2.1.2. Work for a solution

3.2.1.3. How to deal with people

3.2.2. Types of people in the interview

3.2.2.1. ++ Excellent: Concentrate & Cooperative

3.2.2.2. X+ Normal: "Not" Concentrate & Cooperative

3.2.2.3. +X Very Bad: Concentrate & "Not" Cooperative

3.2.2.4. XX Bad: "Not" Concentrate & "Not" Cooperative

3.3. Lecture notes:

3.3.1. Not Concentrate interviewee: Gets out of the scope

3.3.2. The Analyst must meet the customers, while the Developer should not always meet the customer.

4. Lecture 04: How to Analyse the requirements?

4.1. Using a Use-Case Diagram

4.1.1. Scope: inside System-boundary (always imperative verbs)

4.1.1.1. Any thing outside the System-boundary will not be our job

4.1.2. Actors: Main beneficiary of the System (always nouns)

4.1.3. Use-Cases: Actors' actions on the System

4.1.4. Relations between Use-Cases

4.1.5. Relations between Actors and Use-Cases

4.1.5.1. Many Actors can use the same Use-Case

5. Lecture 01: SDLC Systems development life-cycle

5.1. SDLC Phases

5.1.1. Planning :Gathering the Requirements

5.1.2. System analysis :Analyse the Requirements

5.1.3. Design

5.1.4. Development

5.1.5. Testing

5.1.6. Operations and maintenance

5.2. Software development models

5.2.1. Waterfall

5.2.1.1. Advantages

5.2.1.1.1. record keeping

5.2.1.1.2. client knows what to expect

5.2.1.1.3. In the case of employee turnover, waterfall’s strong documentation allows for minimal project impact.

5.2.1.2. Disadvantages

5.2.1.2.1. developers can’t go back

5.2.1.2.2. relies heavily on initial requirements

5.2.1.2.3. change needs to be made, the project has to start from the beginning

5.2.1.2.4. The whole product is only tested at the end

5.2.1.2.5. doesn’t take into account a client’s evolving needs

5.2.2. Agile

5.2.2.1. Advantages

5.2.2.1.1. allows for changes to be made after the initial planning

5.2.2.1.2. up to date with the latest developments

5.2.2.1.3. allows clients to add their feedback

5.2.2.1.4. testing at the end of each sprint ensures that the bugs are caught

5.2.2.2. Disadvantages

5.2.2.2.1. With a less successful project manager, the project can become a series of code sprints

5.2.2.2.2. the final product can be grossly different than what was initially intended

5.3. S.M.A.R.T. Goals

5.3.1. Specific :What do I want to do?

5.3.2. Measurable :How much?

5.3.3. Attainable / Achievable :How can the goal be accomplished?

5.3.4. Relevant / Reasonable :Does this seem worthwhile?

5.3.5. Time-bound :When?

5.4. Lecture notes

5.4.1. One of the differences between agile and waterfall is that testing of the software is conducted at different stages

6. Lecture 02: Scope

6.1. Contracting Phases

6.1.1. Vision Statment

6.1.2. ‫‪Scope‬ :Should we do it or not?‬

6.1.3. Preliminary feasibility study :Should we Go or Not?

6.1.4. Feasibility‬‬ ‫‪study

6.1.4.1. ‪time‬‬ ‫‪schedule‬‬

6.1.4.2. ‫‪budgeting

6.2. Lecture notes

6.2.1. Zero value change scope request. Is a change in the scope but without any addition cost.

7. Course notes

7.1. Scope change request may change the timing and the budget

7.2. RFP: Requests for proposal

7.3. IDSC: The Information and Decision Support Center: Acting as the Egyptian Cabinet Think Tank