1. Class 7 – Inception Phase: Steps & techniques
Group Project 1
GP2 Tips
Inception phase
Steps – overview and process
Organizational Impact form
Non-functional Requirements form
Guest Presentation — Wes Carberry, Sense Corp, Partner
Exercise 7 – Organizational Impact and Non-functional Requirements for Latinitas

2. Group Project 1 4 grades explained appeal process Average 92.1 - 95.5
Min
Max
appeal process 2

3. Group Project 2 : Requirements
Inception – 1st iteration Analysis – Design – Construction - Review
Delivery One-page executive summary
Delivery Strategy discussion summarizing the relevance of the details in deliveries 3 – 9
Delivery Organizational Impact Statement
Delivery Functional Requirements Priorities Table
Delivery Non-Functional Requirements Summary
Delivery Risk Evaluation and Risk Reduction Strategies
Make sure this matches GP2 Spec

4. Group Project 2 : Requirements
Inception – early planning
Delivery 7. Milestone summary (summary of phases)
Delivery 8. Network diagram (overview graphic of phases)
Delivery 9. Gantt chart -- for development team (MS Project)

5. GP 2 – Resources 5

6. GP 2 – Planning Resources6

7. Overview Graphic of Group Project 2 Report
Planning
Tools
Gantt Chart
For Development Team
Network Diagram
Milestone Summary
Analysis Tools
Risk Evaluation and
Risk Reduction Strategies
Funct. & NF Requirements Summaries
For Users &
Management
Org Impact
Strategy Discussion
Group Project 2 report “pieces” -- in order of the final assembled report:
1. One-page executive summary (cover letter)
2. Strategy discussion
3. Organizational Impact Statement
4. Functional Requirements Summary
Non-Functional Requirements Summary
Risk Evaluation and Risk Reduction Strategies
7. Milestone summary
8. Network diagram of your plan
9. Gantt chart
Executive Summary 7

8. Overview Graphic of Group Project 2 Report
Summary of What , Who, When
Gantt Chart
For Development Team
Network Diagram
Milestone Summary
Risk Evaluation and
Risk Reduction Strategies
Justifies Why our plan fits the goals and situation
Funct. & NF Requirements
Summaries
For Users &
Management
Org Impact
Strategy Discussion
Group Project 2 report “pieces” -- summarized by the purpose of each section of your report This section is your explanation of Why your plan is a good one:
1. One-page executive summary (cover letter) Strategy discussion
3. Organizational Impact Statement
4. Functional Requirements Summary
Non-Functional Requirements Summary
Risk Evaluation and Risk Reduction Strategies
These documents provide an overview of your plan
7. Milestone summary
8. Network diagram of your plan This final document is the detail plan for the development team.
9. Gantt chart
Executive Summary 8

9. Overview Graphic of Group Project 2 Process
Case
Brain Storm
Solution
Milestone Summary
(Phases)
Project
Specs
Gantt Chart
Organiza- tional Impact
Network Diagram
(simul-
taneous
phases)
Stake- holders
Task-by-Task
Estimation
Sw / Hw Environments
Functional Require- ments
Root Cause Analysis
Non-Functional Require- ments
Group Project 2 – recommended steps
1st – review the case & GP1 materials (stakeholders, environments, root cause analysis, & DFDs)
2nd – Draft your Org Impact & Requirements Summaries & Risk Evaluation and Risk Reduction Strategies
3rd – 1st meeting: Brain storm your solution and come to a consensus on the functional and non-functional requirements
4th – Create your list of phases (Milestone summary) and figure out what phases can be simultaneous (Network diagram)
5th – Figure out how long each phase will take by completing your Gantt chart with detail tasks and your estimate of the time for each task
6th – Revisit and update your Network Diagram & Milestone Summary list with your Gantt Chart dates
7th – Clean up your early drafts and write your Strategy discussion
8th – Write your one-page executive summary (cover letter)
Context Diagram & DFDs
Strategy Discussion
Executive Summary
Risk Evaluation
and Risk
Reduction
Strategies
Last report task 9

10. How will Group Project 2 compare with the client project ?
Ask for a show of hands.
Resources and Schedule can vary on GP2. We’re not grading based on how easy you get something done in GP2. We grade based on analysis and plan.
On client Project – you actually have to do it. 10

11. Any questions
Ask for a show of hands.

12. MIS 374 SDLC*-- Inception Phase tasks
Final
Construction
Phase(s)
Inception
Phase(s)
1. Identify organizational impacts.
2. Determine project scope, objectives, constraints, performance criteria & risk.
3. Determine initial requirements.
4. Build a development team and create a work plan.
Task order, iteration, and collaboration with users will depend on project characteristics.
This project life cycle is the required model for planning assignments that are part of Group Project 2 and the Client Project.
* SDLC: System Development Life Cycle 12

13. Remember from MIS 301…. What are the 5 Parts of an Information System?
Hardware, Software, Data, AND….Procedures and People!!!
Procedures and People are hardest to change and that’s why non-functional requirements are just as important as functional requirements of your system.

14. Preliminary Investigation Key Steps
Step 0. Identify Stakeholders & Objectives
Step 1. Identify Organizational Impacts
Step 2. Determine
system objectives, project constraints, goals, ROI, risk, and scope.
Root Cause Analysis,
Org Impact, NFR & ROI are techniques to assist with this step.
Step 1 – Perform organizational impact analysis– this is a process to determine how the individual system fits in broader goals. The result is a better idea of what are appropriate objectives and goals for the system. You will also learn information that will influence what you decide are realistic system constraints and risks to be investigated as part of the next step.
For Group Project 2 and the Client Project you will need to determine this fit as part of figuring out the goals and scope of your project.( You will not actually create a strategic information resources plan.)
All should be tied to your Stakeholders

15. Organizational Impact Analysis
This analysis helps you consider the broad goals of the project and how this fits into the strategy, management and organization of the enterprise.
Context
Requirement
Priority
What does this mean for this organization?
What specific characteristics of this system need to be considered?
High, medium, low

16. Organizational Impact Analysis
How will the proposed system (or system enhancement) help the organization improve their competitive advantage?
Strategic
How will the proposed system (or system enhancement) help managers make better decisions?
Management
How will the proposed system (or system enhancement) improve process operations?
Operations

17. Non-functional Requirements
System requirements for enhancements and fixes that require custom development and future upgrades.
Maintainability
System requirements for cross-platform, multi-user agent access, etc.
Portability
System requirements for growth of organization and system usage.
Scalability
System requirements for secure environment and processing--hardware, software, application and user security.
Security

18. Lots of Non functional requirements
Accessibility
Capacity, current and forecast
Compliance
Documentation
Disaster recovery
Efficiency
Effectiveness
Extensibility
Fault tolerance
Interoperability
Maintainability
Privacy
Portability
Quality
Reliability
Resilience
Response time
Robustness
Scalability
Security
Stability
Supportability
Testability

19. Guest Lecturer Wes Carberry MIS graduate (‘99) Sense Corp

20. Org Impact & Non-Functional Requirements (for Latinitas)
Exercise 7
Org Impact & Non-Functional Requirements (for Latinitas)
Work alone or in pairs
Use templates on Resources Page
Turn in online