15-413 SOFTWARE ENGINEERING
MINUTES OF THE ARCHITECTURE GROUP
HELD ON FEBRUARY 9th, 99
Attendance
Role
|
Name/Contact Info. (area code 412)
|
instructor
|
Elizabeth Bigelow
268-8187(Wean 4110), 687-8961(H)
ebigelow@cs.cmu.edu
|
teaching assistant
|
Swati Gupta
422-5340
swati@andrew.cmu.edu
|
team member
absent
|
Nikhil Kanodia
268-1326
nk2g@andrew.cmu.edu
|
team member
|
Kyle E. Jennings
422-5737
jennings+@andrew.cmu.edu
|
team member
secretary
|
Danny Lee
682-1980
dlee@cs.cmu.edu
|
team member
time keeper
|
Chris (Wei C.) Li
621-3840
wcl@andrew.cmu.edu
|
team member
meeting facilitator
|
Ryan Willhoit
862-3405
willhoit@andrew.cmu.edu
|
HLA representative
|
Vincent (Tuyen) Ngo
862-2170
ngo@andrew.cmu.edu
|
Meeting time : Feb. 9th, 99, 6:05pm – 7:10pm
Meeting place : Wean 5336
Next meeting time : Feb 16th, 99, 6:00pm – 7:00pm
Next meeting Place : Wean 5336
Action Plan
Name(s)
|
Action
| Note | All |
a)attend meetings of assigned group
|
|
Ryan
|
a)prepare for agenda for next meeting
b)meet with Elizabeth at least 24 hr ahead
c)set up web server for the group
d)test on web tools and report to the group
|
when machine in 5336 is available
|
Danny
|
a)prepare meeting minutes
b)distribute minutes to members
|
done
done
|
Danny, Chris, Swati, Elizabeth
|
a)meet at Sat. 3pm to discuss about the scenerios and use cases.
|
|
Ryan, Elizabeth
|
a)meet to discuss about the functional requirements
|
|
Elizabeth
|
a)have all group meeting time confirmed
b)work with lab administrator to get stable network configuration
|
|
A.1 Ryan
-
Minutes for last week is passed with spelling corrections
-
Agenda and minutes are put on-line. Will start to set up links for archives and webpages from other groups.
-
The andrew environment is very restrictive to priviledged operations needed for web server setup. Will put the web stuff to machines in Wean 5336 when they become operational.
-
Attended meetings of control and wings/canard/rudder groups.
-
The class need to have standards for diagrams, documentations, libraries, development environment etc.
-
It has been decided that the Wright Flyer Simulation project will be done with C++.
A.2 Elizabeth -
Confirmed that Rational rose can convert diagrams to powerpoint by cut and paste method.
-
The monitor equiped machine in Wean 5336 is running NT, and does not have network connection at the moment. It might be reformatted to install windows 98, which works better with the netbar.
-
The architecture group need to be more concerned with how different groups/parts will fit together rather than with the implementation details.
-
For simplicity, we might need to skip take-off/landing. Most likely the ownership transfer feature is not needed for our project.
-
Need to have scenerios soon so that requirements can be defined. The exact sequences of use cases need to be specified too.
-
The data that will be supplied to us are still not well defined yet. They depend on the government agency, who is generating the data.
-
Has done some library research on aerodyanmics. Has more information for our project than needed.
-
The requirement document need to include :
-
HLA rules
-
functional requirements (Ryan, Elizabeth)
-
scenerios and use cases (Danny, Christ, Swati, Elizabeth)
-
preliminary static and dynamic models
-
physical conditions (environment specifications)
-
structural decomposition of the Wright flyer (specify the components of the flyer)
-
interactions through HLA RTI (Vincent)
-
test flights (test cases)
-
speed of simulation
-
environment control
-
UI input and output
The requirement partially determines implementation constraints.
-
Currently the most important part are : terminology clarification, functional requirements and scenerio/use case analysis.
-
Once the top level design (architecture) is determined, each group will work on their subsystem and produce designs at the lower level.
-
Each liaison need to get glossary from their group and put them in a centralized location.
A.3 Kyle
a) Suggest everyone to browse the webpage reference for configuration management : http://www.cs.cmu.edu/afs/cs.cmu.edu/academic/class/15413-s99/www/CM/doc.
A.4 Danny
-
The event group is very concerned about who will be responsible for the plane’s position and heading. Ryan responded that tentatively the responsibility falls on control and/or wings/canard/rudder group.
-
The event group will experiment with the event publishing and event subscription of RTI services.
-
Through the RTI, the event group will log (script) the simulation sequence.
A.5 Vicent
-
The HLA group is formulating a simple example to demostrate to the class.
-
Also want to make diagrams for the HLA services.
-
Model devised during the TA’s meeting
Share with your friends: |
