Sunteți pe pagina 1din 13

External Entities It is normal for all the information represented within a system to have been obtained from, and/or to be passed onto, an external source or recipient. These external entities may be duplicated on a diagram, to avoid crossing data flow lines. Where they are duplicated a stripe is drawn across the left hand corner, like this. The addition of a lowercase letter to each entity on the diagram is a good way to uniquely identify them. Processes When naming processes, avoid glossing over them, without really understanding their role. Indications that this has been done are the use of vague terms in the descriptive title area - like 'process' or 'update'. The most important thing to remember is that the description must be meaningful to whoever will be using the diagram.

Data Flows Double headed arrows can be used (to show two-way flows) on all but bottom level diagrams. Furthermore, in common with most of the other symbols used, a data flow at a particular level of a diagram may be decomposed to multiple data flows at lower levels.

Data Stores Each store should be given a reference letter, followed by an arbitrary number. These reference letters are allocated as follows:

'D' - indicates a permanent computer file

'M' - indicates a manual file

'T' - indicates a transient store, one that is deleted after processing.

 DESIGN 

System Design

Introduction: - The objective of the system design is to deliver the requirements as specified in the feasibility report. System design involves first logical design (logical design) and then physical construction (detailed design) of the system. The

logical design describes the structure and characteristics of features, such as the outputs, inputs, files, databases, and procedures. The physical construction produces actual program software, files, and a working system. System design goes through two phases of development: -

1. Logical Design

2. Physical Design

Logical Design:- We know that a data flow diagram shows the logical flow of a system and defines the boundaries of the system. Logical design specifies the user need at a level of details that virtually determine the information flow into and out of the system and the required data resources. Logical design describes the inputs, outputs, database and procedures .All in a format that meets the user’s requirements.

Physical Design:- It provides the working system by defining the design specification that tells programmers exactly what that candidate system must do. In short it can state that physical design is the implementation of the logical design. Physical system design consists of the following- 1) Design the physical system i. Specify input, output media ii. Design the database and specify backup procedures. iii. Design physical information flow through the system and a physical design walkthrough. 2) Plan system implementation

Design Notations:-

flow through the system and a physical design walkthrough. 2) Plan system implementation  Design Notations:-

are many specific software development processes that 'fit' the spiral lifecycle model. ISO/IEC 12207 is an international standard for software lifecycle processes. It aims to be the standard that defines all the tasks required for developing and maintaining software.

Testing: Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs (errors or other defects).

Software testing can be stated as the process of validating and verifying that a software program/application/product:

1. meets the requirements that guided its design and development;

2. works as expected; and

3. can be implemented with the same characteristics.

Software testing, depending on the testing method employed, can be implemented at any time in the development process. However, most of the test effort occurs after the requirements have been defined and the coding process has been completed. As such, the methodology of the test is governed by the software development methodology adopted.

Different software development models will focus the test effort at different points in the development process. Newer development models, such as Agile, often employ test driven development and place an increased portion of the testing in the hands of the developer, before it reaches a formal team of testers. In a more traditional model, most of the test execution occurs after the requirements have been defined and the coding process has been completed.

Operations: Operations provide a product or a service to end users. This guide discusses operations from the point of view of their interactions with software maintenance activities and the support activities needed to use the software efficiently and effectively. Software maintenance is the process of modifying a software system or component after delivery to correct faults, improve performance or other attributes, or adapt to a changed environment. Maintenance is always necessary to keep software usable and useful. Often there are very tight constraints on changing software and optimum solutions can be difficult to find. Such constraints make maintenance a challenge; contrast the development phase, when designers have considerably more freedom in the type of solution they can adopt.

Add/edit/delete/activate/deactivate subscription packages

Add/edit/delete/activate/deactivate customers

Add/delete/activate/deactivate admin users

Confirmation email on a registration of a member


View payment transaction history by date range with payment details

View statistics such as

payments received today

number of unapproved/unverified/approved listings

number of categories

number of users

Specific Requirement Analysis:-

Information gathering is usually the first phase of the software development project. The purpose of this phase is to identify and document the exact requirements for the system. The user’s request identifies the need for a new information system and on investigation re-defined the new information system and on investigation re-defined the new problem to be based on MIS, which supports management. The objective is to determine whether the request is valid and feasible before a recommendation is made to build a new or existing manual system continues.

The major steps are:- Defining the user requirements, studying the present system to verify the problem, and defining the performance expected by the candidate to use requirements.

Language (Front-End): .NET FRAMEWORK 2008

Database (Back-End): Microsoft SQL Server 2005

Operating System: Windows NT/2000/XP/VISTA

OPERATIONAL FEASIBILITY It is mainly related to human organizational and political aspects. The points to be considered are:-

What changes will be brought with the system?

What organizational structures are disturbed?

What new skills will be required? Do the existing staff members have these skills? If not, can they be trained in due course of time? Generally project will not be rejected simply because of operational infeasibility but such considerations are likely to critically affect the nature and scope of the eventual recommendations. This feasibility study is carried out by a small group of people who are

Familiar with information system techniques, who understand the parts of the business that are relevant to the project and are skilled in system analysis and design process.

 Project Plan Planning and Scheduling is the detailed study of the various operations performed
Project Plan
Planning and Scheduling is the detailed study of the various operations performed by a system and their
relationships within and outside of the system. During Planning and Scheduling, data are collected on the available
files, decision points, and transaction handled by the present system. The planning and decision making is the good
criteria to the development of the project.
System analysis is simply uses several types of model and System Testing to their development that is why the
project get completed.

Product definition:-

C#.NET  C# language is intended to be a simple, modern, general-purpose, object-oriented programming language. The language, and implementations thereof, should provide support for software engineering principles such as strong type checking, array bounds checking, detection of attempts to use uninitialized variables, and automatic garbage collection. Software robustness, durability, and programmer productivity are important. The language is intended for use in developing software components suitable for deployment in distributed environments. Source code portability is very important, as is programmer portability, especially for those programmers already familiar with C and C++. Support for internationalization is very important. C# is intended to be suitable for writing applications for both hosted and embedded systems, ranging from the very large that use sophisticated operating systems, down to the very small having dedicated functions. Although C# applications are intended to be economical with regard to memory and processing power requirements, the language was not intended to compete directly on performance and size with C or assembly language.


There are no global variables or functions. All methods and members must be declared within classes. Static members of public classes can substitute for global variables and functions. Local variables cannot shadow variables of the enclosing block, unlike C and C++. Variable shadowing is often considered confusing by C++ texts. C# supports a strict Boolean data type, bool. Statements that take conditions, such as while and if, require an expression of a type that implements the true operator, such as the Boolean type. While C++ also has a boolean type, it can be freely converted to and from integers, and expressions such as if(a) require only that a is convertible to bool, allowing a to be an int, or a pointer. C# disallows this "integer meaning true or false" approach on the grounds that forcing programmers to use expressions that return exactly bool can prevent certain types of common programming mistakes in C or C++ such as if (a = b) (use of assignment = instead of equality ==). In C#, memory address pointers can only be used within blocks specifically marked as unsafe, and programs with unsafe code need appropriate permissions to run. Most object access is done through safe object references, which always either point to a "live" object or have the well-defined null value; it is impossible to obtain a reference to a "dead" object , or to a random block of memory. An unsafe pointer can point to an instance of a value-type, array, string, or a block of memory allocated on a stack. Code that is not marked as unsafe can still store and manipulate pointers through the system. Managed memory cannot be explicitly freed; instead, it is automatically garbage collected. Garbage collection addresses the problem of memory leaks by freeing the programmer of responsibility for releasing memory which is no longer needed.

In addition to the try

Multiple inheritance is not supported, although a class can implement any number of interfaces. This was a design decision by the language's lead architect to avoid complication and simplify architectural requirements throughout CLI. C# is more type safe than C++. The only implicit conversions by default are those which are considered safe, such as widening of integers. This is enforced at compile-time, during JIT, and, in some cases, at runtime. There are no implicit conversions between Booleans and integers, nor between enumeration members and integers (except for literal 0, which can be implicitly converted to any enumerated type). Any user-defined conversion must be explicitly


construct to handle exception.

Data flow diagrams:

Data flow diagrams: O-LEVEL DFD Administrator Online mobile store Customers 16


Administrator Online mobile store
Online mobile




Security Requirements

Some of the factors that are identified to protect the software from accidental or malicious access, use, modification,

destruction, or disclosure are described below. Specific requirements in this area could include the need to:

1.1 Utilize certain cryptographic techniques

1.2 Keep specific log or history data sets

1.3 Assign certain functions to different modules

1.4 Restrict communications between some areas of the program

1.5 Check data integrity for critical variables

1.6 Later version of the software will incorporate encryption techniques in the user/license

authentication process.

1.7 The software will include an error tracking log that will help the user understand what error occurred when the

application crashed along with suggestions on how to prevent the error from occurring again.


Communication needs to be restricted when the application is validating the user or license.


Software System Attributes

There are a number of attributes of software that can serve as requirements. It is important that required attributes are specified so that their achievement can be objectively verified. The input system will allow for inputting numbers, operands, special symbols and letters of the alphabet.

Display: - It will help in displaying complete information about mobile code, name, functionalities, and total number of mobiles according to different category.

(2) Customer record: - This module has two parts: -

Search: - This will provide help in searching for records of any customer who has created their profiles during purchasing and payment procedures.

Delete: - This will allow deleting the records of any customer. The deletion can be on the basis of customer id and name.

Online mobile store helps to search for mobiles buy and sell mobiles and also find useful information & resources to help users take wise and an informed decision about mobile phones

The project entitled online mobile store develops a system for the site that focus on all mobile categories including different brands and mobile accessories.

The administrator of the project can Registred the customers because the administrator can lock all status Id.

This enhances the security feature.

The administrator can store different types of data into the database after login.

It is based on users demand.

2.2 User Characteristics

The users should have computer knowledge, and

1. Access to technology

2. Ability to express feelings and ideas in text format

3. Distribution of online interaction

4. Convenience of online interaction

Visitor Section

have authorization to use and to avail any information.

Browse categories

Basic search on homepage

Static information pages like news, faq, about us ,Gallery etc.

Contact form with email notification

Signup (paid or free as per rules set by admin) for customers


Table Of Contents




Purpose of document


Scope of document


Product function overview


Overall Description


Product Perspective


User Characteristics


Operating Environment




Assumptions and Dependencies


Other Nonfunctional Requirements


Performance Requirements


Security Requirements


Software Design Constraints


The name of my organization is Lovely Professional University (Lpu). It has a 600 + Acres Campus: A technology driven campus, spread over 600 + acres of lush green area on NH-1 at the entry of Jalandhar city. LPU provides a Professional learning Environment that acts as a catalyst for the exponential growth of student’s academics as well as extracurricular abilities. LPU is India’s Largest University with 25,000+ students (on one campus) from across 26 States of India and 16 Countries around the world. LPU is duly recognized by UGC and other Apex Bodies and has accreditations of various national and International bodies and associations. LPU has a strong internationalization strategy where LPU wants to be regarded as a university with a global perspective. LPU has 25+ international tie-ups.

 PROFILE OF THE PROBLEM  The profile of the problem is that in previous
The profile of the problem is that in previous time, buying a mobile meant physical going to a store that means
for buying that mobile we had to arrive in the place where the store is located. But now online mobile store can be
accessed from anywhere. The only thing it requires is internet connection.
So with the help of online mobile store we can solve the problem through:-
Referral Tracking:- Track referrals to and from outside professionals as well as referrals made internally within
your organization. Simultaneously track multiple referrals for individual customers.
Guideince Curriculum:-With the Deep Well Data Service (DWDS) Elementary online mobile store Data
System, administrators are able to track their delivered curriculum by date.
As earlier it was not convenient to search for the best mobiles and to find the best match but the online mobile store
gives us better access and it is more convenient. It means he/she will have easy access to the mobiles in the website.
It is an online platform that connecting mobile phones customers.


    I take this opportunity to present my votes of thanks to
I take this opportunity to present my votes of thanks to all those guidepost who really acted as lightening pillars to
enlighten our way throughout this project that has led to successful and satisfactory completion of this study.
We are really grateful to our teacher for providing us with an opportunity to undertake this project in this university and
providing us with all the facilities. We are highly thankful to Mr. Nitin Kumar for his active support, valuable time and advice,
whole-hearted guidance, sincere cooperation and pains-taking involvement during the study and in completing the assignment
of preparing the said project within the time stipulated.
Lastly, We are thankful to all those, particularly the various friends , who have been instrumental in creating proper,
healthy and conductive environment and including new and fresh innovative ideas for us during the project, their help, it would
have been extremely difficult for us to prepare the project in a time bound framework.


This is to certify that ANSHUL BEDI AND CHIMI RAUTELA bearing Registration no.10803483 and






titled, “ONLINE



under my guidance


supervision. To the best of my knowledge, the present work is the result of his/her original investigation and


Signature -:



Lovely Professional University Phagwara, Punjab.

Date :