Docstoc

Detailed Design

Document Sample
Detailed Design Powered By Docstoc
					                                                              iUCF
                                                      Detailed Design
                               Object Oriented Processes for Software Development, Fall 2010


Modification history:

  Version               Date                  Who                             Comment


  v0.0                  08/15/00              G. H. Walton                    Template


  v0.1                  10/20/10              Derek Crane                     Entered basic information (project name,
                                                                              title, group members) and aligned tables.


  V0.5                  10/26/10              Clifton Crane                   Filled in the design issues. Also created a
                                                                              sequence diagram.


  V1.0                  10/26/10              Derek Crane                     Created and added the class diagram. Also
                                                                              added the trace of requirements.




Team Name: iUCF Development Team
Team Members:
        Isidro Arribas, iarribas@ist.ucf.edu
        Jason Bender, jmbender@knights.ucf.edu
        Clifton Crane, fightingpenguinz@knights.ucf.edu
        Derek Crane, derekcrane@knights.ucf.edu
        Renan Pereira, renancpereira@gmail.com


                                                 Contents of this Document
Design Issues
Detailed Design Information
Trace of Requirements to Design


Design Issues:


Performance:
         The application performance when not making web based calls to the online database is optimal. Performance will
vary depending on the user’s wireless internet connection when accessing the database. Performance on the server side of
the system will be optimal as well due to the low number of records stored in the database.

Reuse:
         Application code is specific to development on the iPhone and can only be reused for the purpose of creating
another iPhone application. Server side code used to display information queried from the database to the phone is reusable.
This code can be used for a simple look-up of a record from a table in a database.
Portability:
         Our application is not portable to mobile devices other than different versions of the iPhone. The application is also
not portable to PC or Mac platforms. The server side of our system is portable to other platforms, where the client side
application should still function properly after a required update.

Safety:
         Our system is very safe and risk free to our clients. The client needs to provide no additional information when
purchasing our application from the online store. No information entered into the application by the user will be stored
locally on our server. The client has no way of altering information stored in our online database.

Re-usability:
         Our application has a high degree of re-usability if one wished to develop an iPhone application. It would be
possible to take our existing system and create a similar application where the user can access information relevant to the
application from an online database. Our system has a low degree of re-usability from the point of view of creating a system
not intended to be used on the iPhone.

Maintainability:
         Our application is highly maintainable due to the nature it is delivered to the client. As we make updates to our
software, these updates are made available to new and old customers through the online store. Updates made to the server
side of our system increase maintainability further as these updates will be available to all users immediately.

Testability:
         Our application provides users with a set number of sub-functions, which will increase the testability of our system.
Each sub-function can be tested individually or the system as a whole.


Results of Design Prototype:
         The prototype of our system was designed to demonstrate to our client. The prototype included the user interface of
the main page, a couple sub-functions, and access to our online database. The prototype was successful, and we were able to
demonstrate the displaying of football matches for the current season and the interactive map.


Detailed Design Information
Sequence Diagram:
Class Diagram:
Trace of Requirements to Design:
Requirement No. 1: Search: Satisfied in the server class.
Requirement No. 3: Database: Satisfied in the server class.
Requirement No. 4: PinPointing: Satisfied in the MapGui class.
Requirement No. 5: Settings: Satisfied in the SettingsGui class.
Requirement No. 6: Alerts: Satisfied in the SettingsGui and Application class.
Requirement No. 7: Gui transitions: Satisfied in the GuiElement class via. the changeState() function.
Note: All other requirements in the SRS document not listed above have already been satisfied.
Template created by G. Walton (GWalton@mail.ucf.edu) on October 8, 1999 and last modified on August 15, 2000
This page last modified by <your name here> (<your e-mail address text and link here>) on <modification date here>

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:5
posted:11/16/2011
language:English
pages:5