System Analysis: Software Development Life Cycle Model

2.1 System Analysis

2.1.1 System Development Life Cycle

Analysis

Designing

Development

Testing

Maintenance

Fig:1 Software Development Life Cycle

Software development life cycle or SDLC for short is a methodology for designing, building, and maintaining information and industrial systems. So far, there exist many SDLC models, such as the

 Waterfall model, which comprises five phases to be completed sequentially in order to develop a software solution.

 Spiral model, which is visualized as a process passing through some number of iterations.

 Incremental model is any combination of both iterative design or iterative method and incremental building model for software development. It has seven phases, and

It goes downward through the phases of requirements analysis, design, coding, testing, and maintenance. Moreover, it ensures the design flaws before the development of a product. This model works well for projects in which quality control is a major concern because of its intensive documentation and planning .Stages that construct this model are not overlapping stages, which means that the waterfall model begins and ends one stage before starting the next one.

2.1.2 Study About Project Requirement System requirements study involves a clear and thorough understanding of the product to be developed with the view of removing all ambiguities from customer perception.

There are Three categories of system users interact with our system.

Admin:

Manage Category: Admin can manage Category Registration. In manage, admin can add new category/ Edit existing and delete it.

Manage Product: Admin can manage Product In manage, admin can add new Product/ Edit existing and delete it.

Manage Shop: Admin can manage shop In manage, admin can add new shop/ Edit existing and delete it.

Manage Businessman: Admin can manage Businessman In manage, admin can add new Businessman/ Edit existing and delete it.

Manage Labor: Admin can manage Labor In manage, admin can add new Labor/ Edit existing and delete

 The responsible users of the system and partners are honestly enthusiastic for the new system.

 The changes of this system being operational are quite strong.

2.3 System Requirement

 Software Requirements:

For determination of the system software to be used for preparation of the system, the following consideration has been investigated.

Operating system: Windows Xp, Windows 7/8/8.1/10 Front End tools: Macromedia Dreamweaver8. Database: MY SQL Server: IIS (Internet Information Services) Server

 Hardware Requirements:

RAM: 256 MB Hard disk: 40 GB Processor: Pemtium (R)4 CPU 3.06 GHz

2.4 User Requirements

Functional Requirements:

To avoid the calculation errors the process should be limited to only providing input. Also the input should be in the format of table or database relation. Time required for processing data and presenting user with output should be minima. The functional Requirements are as:

• Business Rules

• Authentication

• Auction Tracking By Date

• Auction Tracking By Product

.

Non Functional