scope: summary of project, what should it do
purpose: details, what problems we have and how do we solve it
overview: summary of purpose
implementation: any extra requirement we added, 5 nonfunctional requirement
only do the use cases model, describe in details: first action what users do…
push back around when car go out the map
visualization(nonfunctional) is not required
turn based on the direction, pick turn randomly, optimal turn is not required
-
What is the target users like background?
-
Are cars allowed to return to the map after entering the local highway?
-
Can turn be determine by randomly?
-
Do we have to model the whole map? Or Graph and edges work already.
Yes. Can change to be a 2D proper map. -
Performance:
-
Supportability and Scalability
-
how much should we include implementation
-
how much of the modeling part should we do?
- Can user change combinations of traffic lights and stop signs during the
simulation?- No,cannot change location of stop sign. Program might crash. Just anadditional requriemen
- Specific example of use case.
- Github stuff.
- Github stuff how do we share with TA or Dr.Bohn
- WE have to use gitlab.
- How many point do we need to list for use case?
- not require alot of point since our project is a simulation program.
- LIst all attribute for UML.
- Start on Sequence diagram.
stopSign: 4 ways, traffic light: 4 ways. how long do we stop? stop immidiately. Car can go immediately if no car. car approach when empty car add to queue list when passing all way stop sign? is stop sign/ traffic light is full way or one way? placement of traffic lights/ stop sign?traffic light need direction? collision? Yes, 3-way intersection? Can be traffic light and stop sign. draw the full sequence diagram? (for stop sign and traffic light)
Each action need a different use case.
- User place a component.
- Start/ stop simmulation.
user case:
- Need actor objeects.'