1 / 6

LECTURE 3 Project Analysis Course H. Afsarmanesh June 2012

LECTURE 3 Project Analysis Course H. Afsarmanesh June 2012. Week 1 Selecting project topic Environment information gathering - focused on project topic Defining goals and scope (vision & mission) of the project (literature study about project) Glossary development

karah
Download Presentation

LECTURE 3 Project Analysis Course H. Afsarmanesh June 2012

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. LECTURE 3 Project Analysis Course H. Afsarmanesh June 2012

  2. Week 1 • Selecting project topic • Environment information gathering - focused on project topic • Defininggoals and scope(vision & mission) of the project (literature study about project) • Glossary development • Stakeholders identification (& user groups)

  3. Week 2 • Designing /suggesting (textual or formal)a few potential use cases and/or scenario descriptions about project • – constituting problem statement– • [* brain storming at group level, and literature study on RE methodology] • Starting with discovery & elicitation process of requirements • Functional Requirements • Non-functional Requirements • System/domain Requirements, e.g. • DB system requirements • Distributed environment • Clouds • Starting with requirement understanding & analysis • Checking & understanding the elicited requirements

  4. Week 3 • Requirement decomposition & prioritization[* brain storming at group level, assuming different stakeholder roles by group members] • Requirements verification [* brain storming at group level] • Considering (& describing)a new (or a changed) requirement • Reflecting & documenting all needed changes • (*starting at item 6 above) [* brain storming at group level] • Starting with specification/modelling of final requirements • Formalization (use UML) • Classes/objects diagrams

  5. Week 4 • Continuing specification/modelling of requirements • Formalization (use UML) • Activity/state diagrams • Sequence diagrams • Finalization of project report(including lessons learned) • Preparation of final presentation

More Related