1 / 6

WEEK 3 – PRESENTATION GUIDELINE

WEEK 3 – PRESENTATION GUIDELINE. Change Management Class Diagram Modeling. Expected Content. Change Management Project documents revisions (Prioritization, Validation Requirements) Finalize use cases and related specifications Identify main e ntities of the environment

gunnar
Télécharger la présentation

WEEK 3 – PRESENTATION GUIDELINE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WEEK 3 – PRESENTATION GUIDELINE Change Management Class Diagram Modeling

  2. Expected Content • Change Management • Project documents revisions (Prioritization, Validation Requirements) • Finalize use cases and related specifications • Identify main entities of the environment • Classes, Attributes & Operations • Class Diagram

  3. Change Management • Managing a change in scenario (stakeholders, requirements,…) • Have necessary modifications and revision (e.g. in context diagram) • Prioritizing the F& NF Requirements • Review the validation of Requirements

  4. Main Entities of the Environment • This part should discuss, the main entities extracted from the revised scenario described above by entities, we refer to things that we want to store information about them. • Example entities can be: students, courses, projects, department, managers, etc.

  5. Classes, Attributes & Operations • In this section, you should identify: • Classes, e.g. student • Attributes making the classes e.g. student name, student age, etc. • Operations associated with the classes, e.g. resister student(), updatestudentrec(), etc.

  6. Class Diagram • Last step draw class diagram, indicating the • relationships (association, composition and aggregation) between the classes • multiplicities between the classes, i.e. (1..*, 0..*, etc.)

More Related