07-11-2012, 12:32 PM
Objective oriented analysis and design Principles of software engineering
Objective oriented analysis.pdf (Size: 1.2 MB / Downloads: 36)
Introduction:
In this project we are going to build a software model for A SIMPLE ADDRESS BOOK. Our main aim of this project is to store the address data of N number of persons and arrange them by using their names and other formats like sort by zip, state, name. By this Address Book Application we are going to store the details of people. It mainly contains the following details
Create a address book, Add a person, Edit a person, Delete a person, Sorting the entries, Open existing address book We are going to implement using the methods and sources of Objective Oriented Analysis & Design and Principles of Software Engineering.
Back ground Work:
The software to be designed is a program that can be used to maintain an address book. An address book holds a collection of entries, each recording a person's first and last names, address, city, state, zip, and phone number. The most important entries to add to a new entry are the Name and zip code
The name entry shows up as a "friendly" name, but there are lots of spaces to
fill in(like home address, working address, home & work phone & fax
numbers etc“) The address book actually has two components;
Sort by name & sort by zip. You specify the address type when you create a , new entry , so you don't need to memorize the address formats
Requirements:
a) User Requirements: It must be possible to add a new person to an address book, to edit existing information about a person (except the person's name), and to delete a person. It must be possible to sort the entries in the address book alphabetically by last name (with ties broken by first name if necessary), or by ZIP code (with ties broken by name if necessary). It must be possible to print out all the entries in the address book in "mailing label" format.
The initial requirements call for the program to only be able to work with a
Single address book at a time.
b) Functional Requirements:
If the user chooses the New or Open menu option, any current address book will be closed before creating/opening a new one. A later extension might allow for multiple address books to be open, each with its own window which can be closed separately, with closing the last open window resulting in terminating the program. In this case, New and Open will result in creating a new window, without affecting the current window. The program will keep track of whether any changes have been made to an address book since it was last saved, and will offer the user the opportunity to save changes when an address book is closed either explicitly or as a result of choosing to create/open another or to quit the program. The program will provide the features like sort by name or zip
Security specification:
Security forms an important aspect of any critical system.
Any security requirement is often ‘shall not’ requirements that define unacceptable system behavior rather than system functionality.
The conventional approach to security analysis is based around the assets to be protected and their value to an organization. A possible security specification process has three basic processes. They are:
1)Asset Identification:
Here the asset can be people details which must be confidential.
The code through which the address book is being generated has to be write protected. The unknown details should be hided.
Reliability
Software reliability specification:
Reliability is a complex concept that should be considered at the system level rather than the individual component level.
Because the components of a system are independent, a failure in one component can cause a system failure.
Here the system being a computer-based system we have to consider three dimensions when specifyin00g the overall system reliability.
1) Hardware reliability:
We need to check the level of hardware failure in a system. In this system the probability of hardware failure is more compared to other systems but it should not be neglected.
2) Software reliability:
How likely is that a software component will produce an incorrect output? Software failures are different from hardware failures in that software does not wear out. It can continue operating correctly after producing the incorrect result. In this system there can be failure in the system due to data errors, same names for persons, same pins can be assigned to the people , linking of the database with the system etc.
3) Operator reliability:
The operators in this system can be a common man. Any one of them are not exposed to the usage of the system it is more likely to cause an error.As all these are closely linked and are interdependent of each other they should not be neglected at any level of system design.
Software Process Model:
Software Process Model is an abstract representation of a software process. Each process model represents a process from a particular perspective, and thus provides only partial information about that process. There are three Software Process Models.