Upload
kory-lawson
View
217
Download
3
Embed Size (px)
Citation preview
Senior Project – CSc 190
Senior Project CoordinatorProfessor Buckley
Riverside [email protected]
Day 2!!!Day 2!!!
2Senior Project Organizational Chart
The SW Development “Company”
Senior Project “CEO”
Professor Buckley
Professor Lan“Divisional Mgr.”
Team 4
Team 2
Team 3
Team 1
Team …
Professor Jin“Divisional Mgr.”
Team 4
Team 2
Team 3
Team 1
Team …
3
More like a “Business” than a class!
• Seminar meetings are like “all-hands” meetings with the company’s CEO - everyone present.
• Meetings with Faculty Project Adviser are like meetings with the Division’s project manager.
• Team meetings are “run” with the team’s project manager providing the organizational focus.
Team is responsible for “managing” the relationship with the sponsor… your customer.
4PROJECT LOG
1. Team Meetings (Agenda and Minutes)
2. Weekly Time and Status Reports
3. Project schedule
4. Weekly Meetings With Project Faculty Adviser (Agenda and Minutes)
5. Meetings with Sponsor / Customer (Agenda and Minutes)
6. Technical Review Summary Reports
7. Baseline Change Requests
8. Cross-references to key decisions
http://gaia.ecs.csus.edu/~buckley/CSc190/ProjectLog.pdf
The “Audit Trail”
5What takes so long?
The “Process”Project Overview
Specification
MgtPlan
Req’tSpec
DesignSpec
BaselineCode
UserManual
System Test Plan& Test Specs
Testing &Test Report
PrepareDelivery CD
Architectural Design
Prototypes
Req’tPrototypes
SPONSOR MTG:Delivery and Sign-off
SPONSOR MTG:Delivery and Sign-offSPONSOR MTG:
Sign-off on Baseline Req’tsSPONSOR MTG:Sign-off on Baseline Req’ts
UsabilityPrototypes
CSc 190 CSc 191
6What do you do in CSc 190 - First
Semester
Activity Deliverable
Identify Project Project Abstract
Prepare Project Overview Project Overview Specification (POS)
Plan Project Project Mgt. Plan (PMP)
Elicit Software RequirementsPerform Requirements Analysis SW Req’ts Specification (SRS)
Prepare Req’t Prototypes Prototypes and Sponsor approval
Prepare for Customer Presentation Baseline Req’ts Review
All “Deliverables” completed and approved by the end of week 15
- last day of instruction -
7
What you do in CSc 191 - Second SemesterActivity Deliverable
Complete software design specification SDS Document
Prepare design prototypes Prototypes and Sponsor approval
Prepare System Test Plan and System Tests STS Document
Implement System Design Baseline CODE
Conduct System Tests & STR Document
Prepare System Test Report
Create User's Manual UM Document
Create Delivery CD Product CD
Prepare for delivery to sponsor Delivery and Sign-off
All “Deliverables” completed & approved by end of week 13
Allow for (and plan for) two weeks of operational use
Sponsor sign-off by end of week 15 – last day of instruction
8
Identifying an Acceptable Customer
• The customer/sponsor must represent a legitimate business, governmental entity, a non-profit organization, or an educational institution.
Not a student project or a faculty “assignment”.
• The team cannot serve as their own customer/sponsor.
• The customer/sponsor must not be related to student.
• None of the project team may work directly for the customer/sponsor.
( the job performance by the team member should not be affected positively or negatively by the team’s work).
9
The “Lab period”
Team meets separately once a week with their “Faculty Adviser”
Meeting time is set by team and Faculty Adviser (15 to 30 minutes)
Agenda:
• Discuss the work completed during the previous week
• Discuss and document problems
• Turn in the staff-hour accounting sheet and schedule updates
• Review work assignments for the coming week
• Review lab instructor’s comments on submitted document drafts
• Negotiate changes in project schedule
Teams are to use a Standard Agenda for each meeting
see Project Log specifications
10
Grades
CRITERIA:
• Demonstration that the team managed the project, week-by-week, throughout both semesters and used the required software engineering principles and practices
• Each team member contributed
• Team took responsibility for the quality of the team’s work
• Team worked effectively with their sponsor throughout the project
• Successful delivery of the software – satisfying the sponsor's “acceptance criteria”
11
COURSE MATERIALS
READ the following:
Introduction – Day 1
COURSE SYLLABUS
COURSE OBJECTIVES / EXPECTATIONS
Memo to Potential Sponsor explaining Senior Project
12
GRADES
CSUS Definition of Grade Symbols (page 103 – CSUS 2002-04 Catalog)
A =Exemplary achievement of the course objectives. In addition to being clearly and significantly above the requirements, work exhibited is of an independent, creative, contributory nature.
B = Superior achievement of the course objectives. The performance is clearly and significantly above the satisfactory fulfillment of course requirements.
13
Senior Project - The Benefits
Provides the opportunities to:
• Apply your CSc knowledge and learning skills as a productive member of a software development team.
• Develop a software product for a real client.
• Accumulate realistic work experience.
• Create a portfolio documenting the quality of your work.
• Begin the transition from academic life to professional life.