FIT2043 Lecture Notes - Lecture 6: Software Architecture, Risk Management
13 Jun 2018
School
Department
Course
Professor
L6 - Project Inception
What Is Inception?
● Initial phase of software development
● Find the scope
○ What’s involved?
○ What are the goals of the project?
● Decide on a team
○ Sort out structure & responsibilities
● Make decision about software process
● Make technical decisions
○ Sketch out software architecture
○ Target hardware platform, language
Project Plan
● A document that contains the information a team needs to manage themselves:
internal
● Has information about the project
○ What is
○ Who is it for
○ What needs to be delivered and when
○ Other systems it needs to work with
○ Who to talk to in other organisations (client, vendors), who is responsible for
talking to them
● Information about the team
○ Who’s in it
○ Roles, responsibilities
○ Who everyone reports to
● Information about the process
○ What is the process being used? Scrum, Spiral
○ Policies for keeping everyone informed - meets? Written reports?
○ How will we allocate tasks to people
○ How will we keep track of the amount of time they are spending
● QA process information
○ What will we QA, how, when and who is charge of it
● Risk management
○ What are the most important risks the project faces you think?
○ How can we prevent this?
○ If problems arise, what will we do about them
● Audience:
○ the team: to understand how the team works and anybody who needs to look
up the team’s policy
○ Management: make sure policies are being followed and help suppose the
rest of the team
● Written by project manager but contains policies to be followed by everyone
● Developed during project inception
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
A document that contains the information a team needs to manage themselves: internal. What needs to be delivered and when. Other systems it needs to work with. Who to talk to in other organisations (client, vendors), who is responsible for talking to them. How will we allocate tasks to people. How will we keep track of the amount of time they are spending. What will we qa, how, when and who is charge of it. If problems arise, what will we do about them. The team: to understand how the team works and anybody who needs to look up the team"s policy. Management: make sure policies are being followed and help suppose the rest of the team. Written by project manager but contains policies to be followed by everyone. What are you going to hand over and when. What tools and techniques are you going to use/. Other team you in you need to collaborate with.
