Project Specification

1
Project Specification
2
project

• The project we are chosen is smaller scale
  projects that a student might take through from
  initial specification to implementation.
• Depending on the time available, these may also
  be considered simply as design projects. In these
  projects, students might be expected to produce
  some of the following documents

3
Project Documentation

• A Software requirements specification. (chap 6)
• User requirements (fig 6.1)
• System requirements
• Structured language specifications form. (fig
  6.12 6.13)
• Sequence diagram (fig 6.14)
• Functional requirement (fig 6.3) (fig 6.6)
• Non-functional requirements (fig 6.3) (fig 6.6)
• Domain requirements (fig 6.7)
• Software requirements document (fig 6.17)
• the structure of a requirements document , (IEEE
  plus Heninger)

4

• A formal specification for part of the project.
  (chap 10)
• Model-based specification (fig 10.11 schema)

5

• An outline architectural design. (chap 8,11)
• Architectural model (fig 8.1)
• Process model (fig 8.1)
• Behavioral model,
• Data-flow diagram (function-oriented pipelining)
  (fig 8.3 8.4)
• State machine models (fig 8.5) plus Stimuli and
  system states. (Fig 8.6)
• Data model
• Semantic Data model data dictionary (fig 8.8
  8.9)
• Object models
• Class hierarchy (fig 8.10)
• Object aggregation (fig 8.13)
• Object behavior modeling (8.4.3 fig8.14 fig7.8)
• Object-oriented decomposition (fig 11.5)

6

• A detailed Data Base specification.
• A test specification. (chap 23)
• System test
• Interface testing
• Test case design
• Test automation
• A user manual and associated help frames.

7

1. A project plan and schedule setting out
   milestones, resource usage and estimated costs.
   (fig 5.3, 5.4, 5.5, 5.6, 5.7, 5.8)

8

1. I would not normally expect student to produce
   all of these documents. You have to chose the
   most appropriate, depending on the orientation of
   your course.
2. Produce the implementation software to show the
   how the result will like.
3. produce a power point presentation to introducing
   your work.
4. members could question each student on their
   work.

9

• Here have some example as followed that explain
  what the project like? You can design by your own
  project use the same way.

10
A police vehicle command and control system

• It is a requirement of a police service that it
  respond as quickly as possible to reported
  incidents and the objective of a command and
  control system is to ensure that incidents are
  logged and routed to the most appropriate police
  vehicle.
• Factors which must be taken into account in
  deciding which vehicle to send to which incident
  include

11

1. The type of incident. Some incidents are more
   serious than others and require a more urgent
   response. It is recommended that classes of
   response be identified and incidents allocated to
   these classes.
2. The position of available vehicles. In general,
   the best strategy is to send the closest vehicle
   to respond to an incident. Take into account that
   the position of vehicles may not be known exactly
   and it may be necessary to send a message to
   vehicles to determine their current position.

12

1. The type of vehicles available. Some incidents
   require a number of vehicles, others such as
   traffic accidents, may require specialized
   vehicles and so on.
2. The location of the incident. In some areas, it
   may be unwise simply to respond to an incident by
   sending a single vehicle. In other areas, a
   single vehicle or policeman may be all that is
   needed to respond to the same type of incident.

13

1. The need to alert other emergency services such
   as fire and ambulance services. The system should
   automatically alert these services if necessary.
2. The system should allow details of the reporter
   of incidents to be logged.

14

• A system such as this one is open to almost
  indefinite expansion. For example, police
  vehicles may include fax terminals so that
  written information may be faxed when a vehicle
  is routed to an incident. A user interface for a
  system control room might be prototyped and so on.

15
An automated road tolling system

• In many countries such as the USA ?Australia and
  France, it is common to have to pay tolls on
  major interstate roads or Freeway. The toll
  applied reflects the distance traveled. However,
  toll stations require vehicles to stop and when
  the traffic is heavy, this can cause significant
  congestion. The aim of this project is to
  automate the collection of tolls from cars using
  communicating road side and on-board computers so
  that there is no need for cars to stop when
  passing a toll station.
• Factors which should be taken into account when
  designing the system are

16

1. Cars may be equipped with an on-board system that
   communicates a car identifier to roadside tolling
   equipment.
2. Smart-card technology is now available that
   allows drivers to buy a card and to 'charge' it
   with credit from an ATM.
3. You need to have a mechanism to charge vehicles
   that are not equipped with an on-board system.

17

1. Toll stations should be situated at
   inter-sections and should not normally be manned.
   They must carry out self-monitoring and report
   faults to a control centre.
2. Number plate cameras can photograph and
   automatically recognize car license plates.
3. The system may have to integrate with other
   computer systems, particularly those that
   maintain car licensing information.

18

• There is scope in this project for various
  simulation exercises to support the system. For
  example, students may be asked to write a
  simulator that mimics the behavior of groups of
  vehicles emitting signals from their on-board
  equipment.

19
Presentation Schedule

• Submit your detail project by 28/May/08 (use
  power point format) and make a Middle
  Presentation on 30/May/08 (you need to complete
  the documentary work),the final Presentation is
  on 20/June and 27/June.

20
End