Final Point Presentation

1
Final Point Presentation
Neha Sathviha John Shrinivas
2
Agenda
An Outline
3
3
Development Process
5
5
Requirements
9
10
1
1
WOP
Reflection
Architecture Design
6
7
7
8
Risk
Implementation Transition
11
2
9
2
8
10
Towards Success
Demo QA
4
4
Configuration Management
3
Wings Over Pittsburgh
What is it ?
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection
Provide your details
I want to participate in the Airshow


È
Director
Participants
gt
4
Working Towards Success
Mapping to TOS
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection
Product Quality
Functional Requirements
Modules Implemented
Authenticate into System
Quality Attributes
Testing and Deployment
Show Air Show Details
Test Cases
Add/Modify Participants
Defect Log
Quality Conformance
Show Participants Data
Security, Usability Modifiability
Maintain Participant data
Update Show Details
gt
TOS Threshold of Success
5
Development Process
Agile Unified Process
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection
gt
6
WOP Schedule
Planned Vs Actual
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection
Available Effort 2112 MH Estimated
Effort 1926 MH Actual Effort 2015 MH
Legend
Phase
Problem
MH Man Hours WOP Wings Over Pittsburgh
7
Configuration Management
The Process
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection

• Before Server Personal repositories on
  individual workstations which were regularly
  synchronized.
• After Server Used a centralized sever and
  individuals accessed through VPN.
• Problem Version incompatibility between the
  Java, Struts and Tomcat sever.

8
Requirements Management
How the Techniques worked ?
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection


Contextual Inquiry
Requirements Specification Artifacts


Requirements Elicitation Techniques


HTML Prototype
Interviewing
gt
9
Risk Management
A Preview
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection
10
Risk Management
Risk Metrics
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection

• Continuous Risk Management in Iterations
• Tracked Risks and Identified Status

SRE Software Risk Evaluation
11
Struts Framework
WOP Architecture
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection

• Driving Force for Selection
• Prioritized Scenarios
• Business Drivers
• Technical Constraints
• Used E-lite Team Decision Making Process

Controller
Model
View
gt
12
Analysis of Quality Attributes
Achieving the QA
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection

• SECURITY

• MODIFIABILITY

• USABILITY

gt
13
Implementation
How did we code?
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection

• Development Methodology
• Iterative development
• Evolutionary HTML prototypes were used
• for further development
• Used pair programming when required
• Use of different tools

gt
14
Testing and Validation
Product Quality
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection
Checklists
Guidelines
Types of Testing
Traceability Matrix
Unit Testing
System Testing
User Acceptance Testing
gt
15
Transition
Deployment of the System
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection

• Deployment at Clients Side
• Application will be provided in DVD
• Installation manual gives step by step procedure.
• Demo will be presented to the clients
• Educating the End Users
• User manual for system users

gt
16
Reflection in a Nutshell
Our Learning
WOP Towards Success Process Schedule
Configuration Requirements Risk
Architecture Design Implementation Testing
Validation Transition Reflection
Technology
Process
People

• Meetings can be effective only if the team is
  well gelled
• Good relationship with the clients is very
  important
• Dont exceed Clients expectations too early
• Single point of contact is both a boon and a bane

• Getting Expert opinion is not always possible
• Defining required information prior hand is more
  beneficial
• Transition Plan helps in organizing and
  coordinating the activities between the team and
  the client

• Risk Management should be rigorous
• Overcame Struts learning Curve
• Learnt Cascading Style Sheets
• MVC architecture helps in modifiability

17
Demo !
18
Questions ?
19
Acknowledgement
Thanks for your help !

• Dr. Lynn Carter (Project Mentor)
• Gil Taran (Project Mentor)
• Ethan Urie (Student Mentor)
• Charles E. Sargent (Client)
• William Sargent (Client)
• Anthony Lattanze (Architecture Consultant )
• Dr. Siva Kumar (Architecture Consultant )
• Mel Rosso Llopart (Presentation Consultant)
• Linda Pesante (Presentation Consultant)
• Poornima Bharathy (Presentation Consultant)
• Ed Walter (System Support)

lt
20
Stakeholders
Stake in the Project
Carnegie Mellon University E-lite Team
Air Show Director
Air Ramp Boss
911 Airbase Reserve Management Team
Wings Over Pittsburgh Air show Participants
Viewers
Wings Over Pittsburgh
Support Group
Carnegie Mellon University Mentors
Dr. Lynn Carter
Gil Taran
Ethan Urie
lt
21
Problem Domain
Current Pain
WOP Problem Development Process Roles
Requirements Threshold of Success
Architecture Risk Measurements
Artifacts Snaps
Provide your details

I want to participate in the Airshow

È
Air Boss

Participants
Director
Support Staff

• Current process is cumbersome
• Miscommunication between the system users
• Inconsistency in executing the Airshow logistics
• Revamping the existing webpage

lt
22
Threshold Of Success
Defining Our Goals
WOP Problem Development Process Roles
Requirements Threshold of Success
Architecture Risk Measurements
Artifacts Snaps
Must should have
Top 3 quality attributes

• Authenticate into System
• Show Airshow Details
• Add/Modify Participants
• Show participants Data
• Maintain Participant data
• Update Show Details

• Security
• Modifiability
• Maintainability

Quality Attributes
Functional Requirements
Product Quality
5 defects per KLOC
lt
23
Development Process
Selection of Process
WOP Problem Development Process Roles
Requirements Threshold of Success
Architecture Risk Measurements
Artifacts Snaps

• Analyzed Different Standard Processes
• Development Process Selection Criteria
• Team Size
• Type of Product
• Project Size and Complexity
• Competent and Experienced Developers

AUP
TSP MSS RUP
XP SCRUM
Adaptive SW Development
Milestone Risk-Driven Models

• Set of Best Practices
• Clean Architecture
• Clear Defined Roles
• Risk Driven

• Good for Small Projects
• Test Driven
• Common Ownership
• Small Iteration

lt
24
Flow Model

• Management Incharge
• Lodging
• Communication Facility
• Food, Water
• Tents
• Vehicle Assignment

• Air show Director
• Prepare Guidelines
• Flight Selection Cancellation
• Allocation of Roles

Guidelines, List
Guidelines, List
Guidelines

• Operations Officer/Airboss
• Order of Performers
• Gas Requirements
• Crew Requiremennts
• Filling Ramp
• Cancellation

Guidelines

• Ramp Boss
• Ground Display Management
• Departure Sequence

• Marketing Director
• Sponsorship

Fuel, Hangar
Guidelines

• Base Operator
• Incoming crew logger
• PPR assigner

• Civil Engineering Squad
• Hangar Requirement
• Fuel Requirement
• Air Stairs

• Public Affairs
• Press Release
• Media Links
• Thank U Letters

FAQ

• Security
• Security Decisions
• Traffic, Parking
• Admittance Rules

Press Release

• Webmaster
• Upload

Security Guidelines
lt
25
Sequential Model

• Participate ? Airshow Registration
  Process Start
• Call to Base Operator
• Registration Form Sent
• Crew Fills Form
• Sends Forms back to base
  operation
• Base Operator enters data into
  sheet
• Assign PPR

lt
26
Cultural Model
lt
27
Use Case Diagram
lt
28
High Level Requirement
Driving Force
WOP Problem Development Process Roles
Requirements Threshold of Success
Architecture Risk Measurements
Artifacts Snaps

• Web Based Project
• Transition from static web page to a logistics
  incorporated dynamic web page
• Supports Multiple Users
• Users span from different environment with
  different levels of usage
• Supports Multiple Platform
• Should support different browsers, Operating
  Systems etc.
• Secure, modifiable and easy to use

lt
29
E-lite Decision
Process Behind Decision

• Considered different alternatives Dictatorial,
  Expert Suggestions, Democratic
• Predominantly democratic approach based on team
  member voting

Inputs from Experts Documents
Elite Team
lt

Decision
Problem
Selection Criteria
Voting
Team Meeting
lt
30
Architecture
Framework Selection
WOP Problem Development Process Roles
Requirements Threshold of Success
Architecture Risk Measurements
Artifacts Snaps
Java Server Faces
Apache Cocoon
JBoss Seam
Apache Struts
Criteria
Type
Good
Good
Good
Very Good
Modifiability
Quality Attributes
No Support
Support
Support
Support
Security
Yes
Yes
Yes
Yes
Usability
Medium
Medium
Medium
Less
Time Limit
Business Constraints
Medium
High
Medium
Low
Learning Curve
Yes
Yes
Yes
Yes
Database MySQL
Technical Constraints
High
Medium
Medium
Medium
Flexibility for Change
lt
31
Quality Attributes

• Security
• Modifiability/Maintainability
• Usability
• Availability
• Performance
• Scalability

lt
32
QA Scenarios

• User wants to view the list of participants
  data the system shows the list in 30 second if
  the maximum size of the total participant list is
  1000.
• User wants to search for a particular
  participants data the system shows the
  appropriate participants data or an error
  message in 30 seconds if the maximum size of the
  total participants list is 1000.
• User wants to access the system System shows
  only that data which he is authorized for based
  on the access control rights.
• Webmaster wants to add the details for the next
  Air Show System must be configured to accept
  the next Air Show Details

lt
33
QA Scenarios

• Viewer wants to view the Air Show details System
  must be available except the downtime for the
  system maintenance which is 4 hours per week on a
  weekday
• User wants to view a particular information
  Required information can be accessed within the
  four clicks
• User (except viewer) wants to perform the
  assigned operations System must be available
  except the downtime for the system maintenance
  which is 4 hours per week.

lt
34
Struts
Framework Selected
WOP Problem Development Process Roles
Requirements Threshold of Success
Architecture Risk Measurements
Artifacts Snaps

• Three Tier Architecture
• MVC Architectural Style

Legend
Query / Response
HTTP Request
HTTP Response
Uses
Association
lt
Data repository / Database
Client (Web Browser)
Server
Java Classes / Libraries
35
Architecture Views
Process View
lt
36
Architecture Views
Deployment View
ltltClientgtgt

• Web browser

HTTP

• Apache Tomcat Server
• Jakarta Struts Libraries
• JSP HTML Files
• Action Controller, Action Forms, Model Classes
• Configuration file
• Resource file

ltltServergtgt Web or Application Server
HTTP
ltltServergtgt Database Server

• Database

lt
37
Usability Criteria's

• Visibility of system status
• Match between system and the real world
• User control and freedom
• Consistency and standards
• Error prevention
• Recognition rather than recall
• Flexibility and efficiency of use
• Aesthetic and minimalist design
• Help users recognize, diagnose, and recover from
  errors
• Help and documentation

lt
38
Detail Design
System Design
WOP Towards Success Process
Configuration Requirements Architecture
Design Risk Implementation Testing
Validation Transition Refection

• Design based on Struts Framework
• Prioritized Scenarios

lt
39
Tools Used
lt
40
Traceability Matrix
lt
41
Information communicated to Client

• Resource Requirements
• Software
• Java - JRE version of j2sdk1.4.0
• MySQL - MySQL Server 5.0
• Java Web Server - Tomcat 4.1( Other web services
  can also be used Web sphere, Web logic Java
  Web Server)
• Hardware
• RedHat Enterprise ES3 server running PLESK 8.01
  control panel.
• Personal
• Atleast two users primarily administrator and a
  support person. Apart from that the webmaster
  should be available during the deployment of the
  system.
• Responsibilities of Client and Team
• Client should deploy the system by March 20th,
  2007
• Report the bugs in a consolidated file
  (preferably excel sheet) to the development team
  by April 7th, 2007
• Note The project is over by March 9th, 2007 but
  as goodwill the team will support the system
  (based on the teams commitment to the program)
  till April 30th, 2007 from their own facilities.

lt