01a - project conceptualization.pptx
TRANSCRIPT
![Page 1: 01a - Project Conceptualization.pptx](https://reader036.vdocuments.mx/reader036/viewer/2022083005/563db7d3550346aa9a8e4f24/html5/thumbnails/1.jpg)
Version 2.0
CSC565SOFTWARE ENGINEERING -
LAB
PROJECT CONCEPTUALIZATION
![Page 2: 01a - Project Conceptualization.pptx](https://reader036.vdocuments.mx/reader036/viewer/2022083005/563db7d3550346aa9a8e4f24/html5/thumbnails/2.jpg)
GOAL
A good project must has goal(s).some business objective worth doing
![Page 3: 01a - Project Conceptualization.pptx](https://reader036.vdocuments.mx/reader036/viewer/2022083005/563db7d3550346aa9a8e4f24/html5/thumbnails/3.jpg)
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](https://reader036.vdocuments.mx/reader036/viewer/2022083005/563db7d3550346aa9a8e4f24/html5/thumbnails/4.jpg)
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](https://reader036.vdocuments.mx/reader036/viewer/2022083005/563db7d3550346aa9a8e4f24/html5/thumbnails/5.jpg)
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](https://reader036.vdocuments.mx/reader036/viewer/2022083005/563db7d3550346aa9a8e4f24/html5/thumbnails/6.jpg)
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](https://reader036.vdocuments.mx/reader036/viewer/2022083005/563db7d3550346aa9a8e4f24/html5/thumbnails/7.jpg)
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](https://reader036.vdocuments.mx/reader036/viewer/2022083005/563db7d3550346aa9a8e4f24/html5/thumbnails/8.jpg)
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](https://reader036.vdocuments.mx/reader036/viewer/2022083005/563db7d3550346aa9a8e4f24/html5/thumbnails/9.jpg)
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](https://reader036.vdocuments.mx/reader036/viewer/2022083005/563db7d3550346aa9a8e4f24/html5/thumbnails/10.jpg)
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](https://reader036.vdocuments.mx/reader036/viewer/2022083005/563db7d3550346aa9a8e4f24/html5/thumbnails/11.jpg)
Thank You