Software Planning  

  Our team is using the Project Metrics to measure the cost of making the software. It is necessary that the development of this project be completed on time, in the mist of also all the minor adjustments. Any delays that occur during the adjustments can be minimized. Also, we need to make sure that the Effort/time factor of all involved is well distributed.

 

Our team decides on using Intermediate COCOMO Model to compute software development efforts as a function of program size and a set of "cost drivers" including subjective assessments of our product, personnel and project attributes. This is the best tool to gauge time and effort needed by us to complete the software.


Class of software project:
Organic

We chose the Organic Mode as it is used to assess relatively small teams working on small projects. On top of that, the product has minimal need for innovation data processing algorithms and it’s expected that the KLOC will not be more than 50.

The set of cost driver attributes is chosen as below

Product Attributes

Required software reliability

1.00 (Nominal)

Database size

1.08 (High)

Product complexity

1.00 (Nominal)

Platform Attributes

Execution time constraints

1.00 (Nominal)

Main storage constraints

1.06 (High)

Virtual machine volatility

1.00 (Nominal)

Computer turnaround time

1.07 (High)

Personnel Attributes

Analyst capability

1.00 (Nominal)

Application experience

1.00 (Nominal)

Programmer capability

1.00 (Nominal)

Virtual machine experience

1.10 (Low)

Programming language experience

1.00 (Nominal)

Project Attributes

Modern programming practices use

0.91 (High)

Use of software tools

0.91 (High)

Required development schedule

1.10 (Very High)

  

Productivity & Effort

 

 

Estimated the number of lines of code (LOC) to be delivered for our program

 

 

2.5 KLOC

 

Calculation of Effort Adjustment Factor (EAF) (Using the table above, the 15 attributes are rated on a 6 point scale from “Very low” to “Very High”.

 

 

EAF (Effort Adjustment Factor)

= 1.00 x 1.08 x 1.00 x 1.00 x 1.06 x 1.00 x 1.07 x 1.00 x 1.00 x 1.00 x 1.10 x 1.00 x 0.91x 0.91 x 1.10

= 1.12

 

Calculation of the effort applied in person months with ai and bi derived from values for the Organic Mode.

 

 

E (Effort) =  ai(KLOC) bi x EAF

                 = 3.2 (2.5)1.05 x 1.12

                 = 9.4 person-months

 

Calculation of the development time with cb and db derived from the Basic Model for the values of the Organic Mode.

 

 

D (Development Time)  = cb (E)db
                                  = 2.5 (9.4)0.38
                                  = 6 months

 

Average staffing of FSP to complete the project in the estimated development time.

 

 

AS (Average Staffing) = E/D
                                     = 14 / 7
                                     = 2 FSP

 

Conclusion:

We need 2 FSP to complete the project in a period of 6 months. However, if we were to have a team of 8 people, we need only 1.5 months to complete the project. As we are not full time software personnel, we give a leeway of another half a month to complete the project. This means that we should be able to finish the project in roughly 10 weeks given.

 

  Intelligent Vehicle Parking System  

Use Cases

Descriptions

1) Booking system

Provides the capability to book parking slots

2) Renew and Extend Time

Allows the driver to renew the duration of the parking timing and also to extend it half an hour before the expiry time

3) Update carpark status

Update the current status of the carpark, which uses the information from 2 use cases, namely the "book parking slot" and "renew and extend time"

4) Display path

Displays the path to the chosen parking slots

5) Compute parking fees

Provides the capability to compute the parking fees of the driver

6) Maintain system

Provides the capability to make changes to the system

7) Barrier System

To open or close the entry to a particular designated carpark slot chosen by the driver

 

 

 

 

 

  Carpark Status System  

Actor

Descriptions

1)  Carpark status system

An external system to update the status of the carpark according to the type of slots available and the time of entry

 

 

Use Cases

Descriptions

1)  Premium slot allocation

This use case is started by the carpark status system. It allocates a premium slot to car user

2)  Normal slot allocation

This use case is started by the carpark status system. It allocates a normal slot to car user

3)  Update carpark vacancy

This is the use case started by carpark status system. It updates the system of the number of slots available for both normal and premium slots

  Compute Parking Fees  

 

Actors

Descriptions

1) Update Carpark Status

Person who is the main user of the system

2)  Billing System

Display amount of parking fees that driver must pay.                        

    Amount = no. of premium hrs * premium rate

                           OR

    Amount = no. of peak hrs * peak rate +

                      no. of non peak hrs * non peak rate

 

Use Cases

Descriptions

1)  Slots allocated

Ensure that slots is allocated successfully

2)  Premium Rate

Charge the driver at premium rate. Keep record of the number of hrs charge at premium rate

3)  Normal Rate

Charge the driver $2 for the first hour, then subsequently at normal rate

4)  Peak Hrs

Keep record of the number of 1/2hrs charge at peak hour rate

5)  Non Peak Hrs

Keep record of the number of hrs charge at non-peak hour rate

 

  Renew and Extend Time  

Actor

Descriptions

1) Timing System

An external system responsible for renewal and extension of parking time

  

Use Cases

Descriptions

1) Compute expiry time

Provides the capability to compute the expiry time of the parking slot from the time of booking

2) Extend time

Provides the capability to extend parking time

 

 

 

1
Hosted by www.Geocities.ws

1