Posted below is minutes of our meeting for CS2103T project today. After reviewing the content of today's meeting, I have to say we are amazing! As you can see, we've iendtified a clear purpose of this project, sketched out the basic structure of our program and cleared understanding problems with Dr.Bimlesh this afternoon. I'm glad to have Darren and Qin Chuan in the team and work together with them. They both have few years experience in programming and help me broaden my vision in analyzing problems during our discussion today. I hope we can keep a cordial working relationship this semester and try our best to design a good qualified product!
Happy Chinese New Year to all of you!
Analysis and Planning for CS2103T Project |
|
Minutes | 20/01/2012 | 13:20~14:20 | COM2/108 |
|
|
|
|
| Meeting called by | Darren-Gavin Ho |
|
| Type of meeting | Problem-solving, planning |
|
| Facilitator | - |
|
| Note taker | Zhang Xi |
|
| Timekeeper | Teh Qin Chuan |
|
| Attendees | Darren-Gavin Ho, Teh Qin Chuan, Zhang Xi |
|
|
|
|
Agenda topics |
|
| <> > 1. PURPOSE OF CS2103T PROJECT | <> > | <> >
|
| | <> >
| <> >
|
- Our program will be designed as a desktop utility, which provides a systematic solution for event organizer to book venue, plan event, calculate budget, broadcast events and receiving registrations from both facilitator and participants.
| <> >
|
| | <> > | <> > | <> >
|
| - | <> > - | <> > - | <> >
|
|
| <> >
|
| 2. REQUIREMENT ANALYSIS | |
|
| Discussion |
|
|
- Model the process of organizing an event and sketch out the flow chart
|
|
- Identify types of users: Organizer, facilitator, participant
|
|
- Identify main functions of the program:
ü Organizer: create, delete, modify events ü facilitator/participant: subscribe events ü Retrieve and display latest event information in user interface |
|
- Analyze the required information to create an event:
ü Name of event ü Venue ü Time ü Content (flow of programs to be held in the event: time,programs) ü Budget calculator (items to buy: food, prizes, gifts etc) ü Facilitator (limit number) ü Participants (limit number) ü Submit/ Save as draft |
|
| Action items | Person responsible | Deadline |
|
- To research on the problems of organizing an event
- To add in necessary functions based on research result
| All attendees | Ongoing |
|
|
|
|
|
|
| 3. SYSTEM DESIGN | |
|
| Discussion |
|
- In order to apply OO techniques, we decide to store all the information in view of objects in text files and create a fold called 'database' to keep all text files, instead of using any database servers
|
- Darren proposed to design the program with 3-tier model :
ü GUI ü Controller ü Actual program code |
- Data structure : Array list
|
|
|
| Action items | Person responsible | Deadline |
- Think about algorithms/computations
| All attendees | Will be discussed in next meeting |
- To research on calendar implementation (flash, table or other tools)
| All attendees | Ongoing |
|
|
| 4. PROPOSAL COMPONENTS | |
| Discussion |
|
- Components to be included:
ü Problem statement, solutions ü Case Diagram ü Domain Model (UML) ü Mock user interface ü Sample input data ü Sample output data ü Implementation schedule |
|
|
| Action items | Person responsible | Deadline |
- Details and delegation of work will be discussed in next meeting
| - | - |
|
|
| | | | | | | | | | |
No comments:
Post a Comment