project requirements cop 4331 oo processes for software development © dr. david a. workman school...
TRANSCRIPT
Project RequirementsProject Requirements
COP 4331
OO Processes for Software Development
© Dr. David A. Workman
School of EE and CS
University of Central Florida
March 22, 2007
Revised: 26 March 2010
March 26, 2010
Development Process
Decide onSim Problem
1.0 AnalyzeProblem Req/mts(interviews withDr. Workman)
2.0 DevelopUse Case Diag
Of Virtual World
3.0 DevelopClass Diag of
Virtual World
4.0 DevelopSimulation
Design
5.0 HoldDesign Review
6.0 ReviseSimulation
Design
UpdateSoftware Design
Specification
10.0 DeliverCode, User Guide,
Software Design Spec& Development Log
11.0 GiveProject
Presentation &Demonstration
Nextslide
NOTE: Code and Unit testing should be done usingthe "pair programming" concept. That is, one personwrite the code, another member of the team test thecode according to the design spec.
Begin work onSoftware Design
Specification
8.0Code & Unit
Test
9.0 Integration&
System Test
Lab4-1 Deliverables
Lab4-2 Deliverables
March 26, 2010
Develop Simulation Design
Identify AgentsIdentify PassiveObjects/Classes
Design AgentInteractions
AndState Models
Design MessageClasses
exit
Design incomplete
Detailed DesignAgent Classes
enter
Detailed DesignPassive Classes
NOTE: The iterative design loop should be a group problem solving effort.
NOTE: Detailed design of Agent and Passive classes shouldbe allocated equitably to team members using the concept of"pair programming" one person's detailed design is reviewedand verified by the member(s) of the team.
4.1
4.2
March 26, 2010
Development Schedule
Time
Activities
End Week 1 End Week 6(Final Week)
End Week 5End Week 4End Week 3
Design
Code &Unit Test
Integrate
Document
DesignReview
Gantt Chart
DeliveryDemo &PresentationLab4-1 Due!
Lab4-2 Due!
End Week 2
March 26, 2010
Other Requirements• High-level design and architecture should be developed as a group effort as
follows: individuals develop a design then meet to compare designs and make modifications until a consensus is reached. The architecture and design shall follow the conventions and framework defined in the lecture notes on discrete event simulation.
• Detailed design, code and unit testing, and all documentation efforts should follow a "pair programming" paradigm; that is, each individual is assigned a class, method, section to write or test (review) – the author and tester/reviewer are always different members of the team.
• A daily log of effort shall be maintained by each team member. This shall be done using a spreadsheet similar to the one provided for Lab2. Separate rows shall be inserted in the spreadsheet for each module that has to be designed, coded or tested. Separate rows on the spreadsheet shall be inserted for each document that has to be delivered.
• OO Data Design Format and Protocol shall be followed for all virtual world classes and objects that must be input from an external file or be written to some external media.
• Reuse IOMgmt and SimMgmt as is!
March 26, 2010
Other Requirements• Post Simulation Report
Each project team shall define a simulation purpose or objective(s) that is measurable. This objective shall provide useful feedback or insight to the simulation user regarding the dynamics of the virtual world. Results provided by the post simulation report shall be useful in answering questions relating to the purpose of the simulation.
For example, in the Alien War Simulation, the purpose might be to evaluate the effectiveness of different battle strategies. In the Golf Game simulation, one might want to study the difference in scores among players with the same skill having tendencies to slice or hook the ball on each hole (what type of player does the course tend to favor?) In Texas Hold'em or any other card game, the purpose might be to evaluate the effectiveness of different playing stategies. For the Conference simulation, management may want to optimize the satisfaction of attendees as a function of the number of servers and/or the strategy they use to distribute food and drink to guests – all this while minimizing cost – what is the maximum guest satisfaction per dollar.
March 26, 2010
Deliverables1. (Lab4-1) Software Design Specification (template provided)
2. (Lab4-1) Project Development Plan Lists the design, coding, implementation and documentation tasks assigned to each
member of the team.
3. (Lab4-2) System Source Code
4. (Lab4-2) Test Cases (each individual) and Test Files (each individual)(template provided)
5. (Lab4-2) System User's Guide (template provided)
6. (Lab4-2) Project Development Log (each individual) (template provided)• Line items for each documentation task by the individual
• Line items for each class or method designed
• Line items for each class or method written
• Line items for each class or method tested
7. (Lab4-2) Project Demo (Team presentation)(template provided)