System Design Analysis: Structured System Design Analysis Methodology

3.1 Structured System Design Analysis Methodology
Structured System Design Analysis Methodology (SSADM) will be adopted as software. The methodology will help achieve the objective of the system implementation. The model to be used is waterfall model, which is a sequential software development process, in which progress is seen as flow gradually downwards through the phases of Requirement which is a description to be developed system. Analysis encompasses that task that goes into determining the needs and conditions to be met. Design refers to all the activities involved in conceptualizing, framing, implementing, commissioning and modifying .Implementation, Verification and Maintenance. It will provide a structured approach .The model itself

• Get the end-user involved.
• Identify requirements
Questionnaire
It is the technique used to extract information from number of people. This method can be adopted and used only by a skillful analyst. The Questionnaire consists of series of questions framed together in logical manner . The questions are simple, clear and to the point. This method is very useful for attaining information from people who are concerned with the usage of the system and is a very cheap source of fact finding .
Observation
Unlike the other fact finding techniques, in this method the analyst himself visits the organization and observes and understand the flow of documents, working of the existing system, the users of the system etc.
Used to validate the data collected from other methods and when the complexity of the system prevents a clear explanation by the End-users.

3.3 System Specification
3.3.1 User

Functional Requirements should include:
• Descriptions of data to be entered into the system in this case the client is to input booking details while the administrator is to enter the details of vacant accommodation
• Descriptions of operations performed by each screen in this case there is the client and the administrator side
• Descriptions of work-flows performed by the system. Backing up and updating describes the work flow in the proposed system.
• Descriptions of system reports or other outputs the system is to output details of transactions of the booked rooms by the client.
• Who can enter the data into the system- The administrator and clients are the only privileged personnel allowed to input data
• How the system meets applicable regulatory requirements the system can revoke rooms that have been booked from the client details to avoid double booking.
The Functional Requirements Specification is designed to be read by a general audience. Readers should understand the system without a particular technical knowledge requirement to understand the document.
3.3.3 Design