software engineering project: research expert prabhavathi kumarasamy joshua thompson paul varcholik...
Post on 12-Jan-2016
220 Views
Preview:
TRANSCRIPT
Software Engineering Project:Software Engineering Project:Research ExpertResearch Expert
Prabhavathi KumarasamyJoshua ThompsonPaul Varcholik
University of Central Florida
Presentation OutlinePresentation Outline J. Thompson……………Concept of Operations
P. Varcholik……Software Requirements Specification
J. Thompson……………Test Plan
P. Kumarasamy …………Project Management Plan
Concept of OperationsConcept of Operations
Proposed SystemProposed SystemNeeds
◦ Web-Based system for organizing academic papers
◦ Search and browsing◦ Meta-data
Keywords, author, publication source, abstract (full-text), date of publication
◦ User-provided reviews◦ Annotated references to related
documents◦ Multi-user collaboration◦ Multiple repositories
Concept of OperationsConcept of Operations
Proposed SystemProposed SystemUsers and Modes of Operation
◦ Read-Only User Can view, but not modify items in a repository
◦ Read-Write User Can add, modify and delete items in a repository
◦ Admin User Can manage repository membership and permissions
◦ Repository Owner The user who initially established the repository, though
ownership may be transferred to another user by the site administrator
Can assign admin privileges to other users of the repository
◦ Site Administrator Controls the operations of the entire web application Resolves technical issues, deletes users and repositories, and
transfers repository ownership
Software Requirements SpecificationSoftware Requirements Specification
OverviewOverviewSoftware to be Produced:
◦ Web-based user interface (ASP.NET/C#, HTML and CSS)
◦ Database API (C#)◦ Database (SQL)
Assumptions◦ Client Side
Microsoft Internet Explorer 7 (IE7)
◦ Server Side Windows Vista, Windows Server 2003, or Windows Server 2008 Microsoft Internet Information Server 7 (IIS7) w/ ASP.NET
configuration Microsoft SQL Server 2005 (any edition, including SQL 2005
Express) .NET 2.0 Framework
Software Requirements SpecificationSoftware Requirements Specification
OverviewOverviewStakeholders
◦ Chris Centelle – Customer/User◦ Academic Research Community – Users
55 Requirements◦ 42 Functional◦ 3 Interface◦ 3 Physical Environment◦ 1 Users and Human Factors◦ 2 Documentation◦ 3 Resource◦ 1 Security
Software Requirements SpecificationSoftware Requirements Specification
Use CasesUse Cases
Test PlanTest Plan
OverviewOverviewVerify that the system satisfies all
requirementsTesting will be done on standard PCs
with IE7Testing Phases
◦ Test Sessions Run after coding milestones
◦ Beta Period Begins after system is ‘feature complete’
◦ Acceptance Testing Begins after all show-stopper and normal bugs are
addressed
Test PlanTest Plan
Stopping CriteriaStopping CriteriaTesting Session
◦ All tests have been run (passed or failed)◦ Fatal error occurs preventing further
testingBeta Period
◦ Only known-shippable bugs remain, and code coverage > 70%
Acceptance Testing◦ Customer approves of the system◦ Budgeted time exhausted
Project Management Plan:Project Management Plan:
Software Lifecycle ProcessSoftware Lifecycle Process
Outline Description
Specification
Development
Validation
Initial Version
Intermediate Version
Final Version
Concurrent activities
Evolutionary Development
Project Management Plan: Project Management Plan:
Applicable StandardsApplicable StandardsCoding Standards
Microsoft .NET Design Guidelines for Class Library Developers http://msdn.microsoft.com/en-us/library/czefa0ke.aspx
Artifact Size MetricsC#/ASP.NET◦ Lines of Code (code, comments, blank lines)◦ Number of classes, files, and assemblies
Database◦ Number of tables, views, and stored procedures
Testing◦ Number of unit tests
Project Management Plan: Project Management Plan:
Technical Progress MetricsTechnical Progress Metrics Requirements Phase
◦ Total number of requirements, the number of requirements by priority divided into high, normal and low, total number of tests created.
Design Phase◦ Number of design documents produced, total number of tasks
generated.
Implementation Phase◦ Estimated time vs. actual time (measured in 1 hour increments).
◦ Number of on-time tasks and over-estimated tasks.
◦ Running list of tasks (number of tasks): Not started, In-Progress, Completed, Cancelled.
Testing Phase◦ Number of tests runs, passed and failed.
Deployment Phase◦ Number of submissions sent to the customer.
Project Management Plan: Project Management Plan:
PERT ChartPERT Chart
M3
Coding
Testing
Specification
Design Plan
Test Plan
M1 M2Start
09/17/08
Requirement Analysis
10/01/08 11/05/08
Finish 12/05/08
14 days
14 days
14 days 30 days
30 days
30 days
Beta (Testing & BugFixing)
26 days
Final Documentation
Deployment
9 days 9 days
11/6/08 – 12/1/08
M1, M2,M3 – Milestones
- Critical path
top related