Chapter 2 : System Analysis - SAKET-SK/Online-Electronic-Store-Project GitHub Wiki

After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing system, and the other is to understand the requirements and domain of the new system. Both activities are equally important, but the first activity serves as a basis for giving the functional specifications and then the successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking, and understanding of the existing running system is also difficult; improper understanding of the present system can lead to diversion from the solution.

Analysis Model

The design starts after the requirement analysis is complete, and the coding begins after the design is complete. Once the programming is completed, the testing is done. In this model, the sequence of activities performed in a software development project is: -

  • Requirement Analysis
  • Project Planning
  • System design
  • Detailed design
  • Coding
  • Unit testing
  • System integration & testing

Here, the linear ordering of these activities is critical. End of the phase, and the output of one phase is the input of the other phase. The output of each phase is to be consistent with the overall requirement of the system. Some of the qualities of the spiral model are also incorporated, like after the people concerned with the project review the completion of each phase, the work done.

WATER FALL MODEL was chosen because all requirements were known beforehand, and the objective of our software development is the computerization/automation of an already existing manual working system. Below is how our planned Waterfall model.

image

Study of the System

GUI’S: In the flexibility of the uses, the interface has been developed with a graphics concept in mind, associated through a browser interface. The GUI at the top level has been categorized as

  1. Administrative user interface
  2. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is practically part of the organizational activities and which needs proper authentication for the data collection. The interfaces help the administrations with all the transactional states like Data insertion, Data deletion, and Data updation, along with extensive data search capabilities. NUMBER OF MODULES

The system, after careful analysis,s has been identified to be presented with the following modules: This project is divided into 9 modules:

  1. Registration Module
  2. Products Browse Module
  3. Products Search Module
  4. Shopping Cart Module
  5. Shipping & Billing Module
  6. Payment Module
  7. Admin User Management Module
  8. Admin Catalog Management Module
  9. Admin Order Management Module

Entities Involved in the Project:

  1. Customer
  2. Product
  3. Website Administrator
  4. Operator
  5. Order

Customer: The target user of the system. A Customer is responsible for registering them to the site, browsing site, placing orders and making payments.

Product: Product is the entity, a customer is looking for. A Product will be sold to the customer.

Website Administrator: An entity responsible for managing users, roles, and role privileges.

Operator: The Operator is a person (entity) responsible for managing products and orders. Order: Order is an entity that describes the business transaction.

Hardware and Software Requirements

HARDWARE REQUIREMENTS:

  • PIV 2.8 GHz Processor and Above
  • RAM 512MB and Above
  • HDD 20 GB Hard Disk Space and Above

SOFTWARE REQUIREMENTS:

  • WINDOWS OS (XP / 2000 / 200 Server / 2003 Server)
  • Visual Studio .NET 2005 Enterprise Edition
  • Internet Information Server 5.0 (IIS)
  • Visual Studio .NET Framework (Minimal for Deployment)
  • SQL Server 2000 Enterprise Edition

Proposed System

To debug the existing system, remove procedures that cause data redundancy, and make the navigational sequence proper. To provide information about audits on different levels and also to reflect the current work status depending on the organization/auditor, or date. Required to build a strong password mechanism.

Input and Output

The main inputs, outputs, and major functions of the system are as follows

INPUTS:

  • Customer enters his or her user ID and password.
  • Operators enter his or her user ID and password.
  • Admin enters his or her user ID and password.
  • User requests the product description.
  • User requests the product search.
  • User orders the product.
  • System requests shipping & billing address.

OUTPUTS:

  • Customer receives personal and order details.
  • The operator receives the personal details.
  • Admin receives order details.
  • Users receive requested product details.
  • Users receive orders.
  • System processes orders.

Process Models with Justification

ACCESS CONTROL FOR DATA THAT REQUIRES USER AUTHENTICATION

The following commands specify access control identifiers, and they are typically used to authorize and authenticate the user (command codes are shown in parentheses)

USER NAME (USER)

The user identification is what is required by the server for access to its file system. This command will normally be the first command transmitted by the user after the control connections are made (some servers may require this).

PASSWORD (PASS)

This command must be immediately preceded by the user name command, and, for some sites, completes the user's identification for access control. Since password information is quite sensitive, it is desirable in general to "mask" it or suppress typing it out.