01a - project conceptualization.pptx

11
Version 2.0 CSC565 SOFTWARE ENGINEERING - LAB PROJECT CONCEPTUALIZATION

Upload: wanya64

Post on 05-Jan-2016

4 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: 01a - Project Conceptualization.pptx

Version 2.0

CSC565SOFTWARE ENGINEERING -

LAB

PROJECT CONCEPTUALIZATION

Page 2: 01a - Project Conceptualization.pptx

GOAL

A good project must has goal(s).some business objective worth doing

Page 3: 01a - Project Conceptualization.pptx

WHY?

Every project needs at least one good goal to existSome projects have multiple goalsThe goals also are known as the project mission

Page 4: 01a - Project Conceptualization.pptx

GOALS COME FROM…

Brainstorming sessions among colleaguesResearching market trends and literatureAnalyzing the competitionInterviewing customersSurveys at conventions or trade showsFeedback from user groups

Page 5: 01a - Project Conceptualization.pptx

GOALS ARE CLEAR IF THEY…

are a deliverableare measurable and testablestate the action needed to achieve the goal (build, deploy, etc.)are conversational (can be explained)are reasonable and doableare communicated and published as part of the project charter

Page 6: 01a - Project Conceptualization.pptx

GOAL TO MISSION…

Customers must determine whether the project mission:

identifies the business functions to be automatedhas clear benefits (fills a need or takes advantage of an opportunity)

The Executive Sponsor must get a good sense of the:

intent of the projectproject scope, schedule and resource utilization

Page 7: 01a - Project Conceptualization.pptx

DETERMINE SCOPE OF WORK

Uncover hidden assumptions among team members:

For each goal, brainstormwhat it is and make it a listwhat it is not and make it a list

Use both lists toclarify assumptionsset boundary conditions

Page 8: 01a - Project Conceptualization.pptx

WHY?

The project mission also helps determine the software requirements

A software requirement is a capability that someone wants

Page 9: 01a - Project Conceptualization.pptx

THEN…

Since requirements will be used for development, they should also be:

Complete – have all significant requirementsConsistent – all documents internally consistentChangeable – changes are a fact of lifeTraceable – a requirement can followed from its source to its fulfillment in design and code

Page 10: 01a - Project Conceptualization.pptx

LASTLY…

A list of requirements further helps:Form agreement on what the system should doProvide a basis for planning the technical content of software solutionsGive developers a better understanding of the system

Page 11: 01a - Project Conceptualization.pptx

Thank You