Week 7 of SAD

Well i got two comments last week. I'm amazed! I'm also amazed that POD read my blog.

Week 7 - Finishing analysis
On completion of this session you should be able to:
• Prioritize the system requirements based on the desired scope
and level of automation for the new system
• Describe the strategic decisions that integrate the application
deployment environment and the design approach for the
new system
• Determine alternative approaches for system development
• Describe the key elements of an RFP
• Develop a professional presentation of results to management

This week basically talked about writing an analysis report..very useful for the first assignment.
A short lecture, only 30 slides. Apparently i didn't take any notes.

The study guide is quite sussinct for this unit also.

My summary:

• systems analsyists dont' develop documents from scratch, they use templates. Great news. i like templates. They break up your problem (a report for submission) into smaller problems (an introduction, a scope outline, a use case diagram etc.).
• scope creep is a term used to describe scope running out of control. Defies the purpose of scope. It is a common cause of project failure, too many functions included into a project.
• Scope is done by the analysit with plenty of discussion with the stakeholder(s)
• the unit guide talks about function points in relation to assertaining the cost and effort involved in a new project. this directly relates to our work in Software Engineering. Interesting how it all seems to be linked in second year.
• Application deployment environment - this i don't understand. must do more research
• Dealing with vendors: an anylist will create a document called "request for proposal" to communicate with vendors what the project needs from them and to find out how much it will cost and what the vendors will provide. This i have experience in at work. I deal with vendors on behalf of projects all over the place. I see more the proposal for services itself, rather than the request for proposal. I assume that these are created with discussion between vendors and project managers and stakeholders.
• typo in the study guide? Under heading "Presenting the Results":
• Analysts make a variety of presentations through the life of a project, some
  are formal and others information.
• should this not be formal and informal, rather than formal and information?
• powerpoint is the overwhelming favorite in presentations.

summary: this unit wasn't actually about writing the analysis report, it was about finalising analysis before writing the report.