OBJECTIVE OF PROJECT The main objective of the project is to help the ongoing user help to attain an easy way to navigate the customer’s details and solve the Customers problems. The Disadvantages of the cellular phone is that same of that with the other electronic gadgets. If damaged or gets faulty by any means then the entire system gets Hung up. The main objective is to provide an easy, manageable way to provide help to the customer. It is basically a very swift complaint processing System by which customer can again get the device back in the right condition. It’s basically build in the platform of C#.NET windows application which makes the application quite flexible and easy to be operated. The manager of the Mobile store also finds it sufficient enough to view the details of the sales, servicing and well organized way to employ the staff that are included in the mobile store itself. Thus it can be highlighted that the MOBILE SHOP MANAGEMENT SYSTEM is the self explanatory package of governing a well developed Mobile
Transcript
OBJECTIVE OF PROJECT
The main objective of the project is to help the ongoing user help to attain an easy way to navigate the customer’s details and solve the Customers problems. The Disadvantages of the cellular phone is that same of that with the other electronic gadgets. If damaged or gets faulty by any means then the entire system gets Hung up. The main objective is to provide an easy, manageable way to provide help to the customer. It is basically a very swift complaint processing System by which customer can again get the device back in the right condition. It’s basically build in the platform of C#.NET windows application which makes the application quite flexible and easy to be operated. The manager of the Mobile store also finds it sufficient enough to view the details of the sales, servicing and well organized way to employ the staff that are included in the mobile store itself.
Thus it can be highlighted that the MOBILE SHOP MANAGEMENT SYSTEM is the self explanatory package of governing a well developed Mobile Store in such a way that nothing gets excluded or rather neglected from the project and everything is predominant over necessary requirements that meets the need of both Customer as well as User.
Hardware Requirements
Processor : Pentium-iv
RAM : 1GB
Hard Disk : 40 GB
Printer : HP Laser Zet
Monitor : LG Monitor
Software Requirements
Back end : MS excess
Front End : Visual Basis
Work Station O/s : Windows XP
Tool : M. S. Office
2 | P a g e
Feasibility Study Feasibility is the determination of whether or not a project is worth doing. The process followed in making this determination is called a feasibility study. It identifies, describes and evaluates the candidate system and selects the best possible action for the job. The suggested system will run on Client server architecture. We want to develop the system using ASP.NET /Java and Oracle or SQL Server .We knows that .NET framework is provided and available on most of the systems. Similarly Java runtime environment is present in all Web Servers. Most modern web browsers are .NET and Java enabled. The proposed system will be modular, so it will be easily maintainable, it will be able to support many users at the same time. The security is very cautiously maintained. The system can be easily developed many skilled professionals are available. .NET allows multi language integration so differently skilled persons can be used to develop different modules. Similarly the existing working of the Airline System needs not being harmed. The user need not be trained. Any person who accustom to the internet can use the system .The cost of developing the system is minimal. The existing database of the Airline System can be used without creating new one. The customers get more benefits from the internet facility of the Airline System and they also can reduce their branch overheads though also the manual facilities should be available.
As said in the previous introduction the feasibility analysis is the procedure that identifies, describes and evaluates proposed systems and selects system for the job. It consists of various analyses done in order to
3 | P a g e
determine the viability of the proposed system. Then what the actual need of the feasibility analysis it is described as below.
Need of Feasibility Analysis
An initial investigation culminates in a proposal that determines whether an alternative system is feasible or not. A proposal summarizing the thinking of the analyst is presented to the user for review. When approved the proposal initiates feasibility study that describes and evaluates proposed systems and provides for the selection of the best system that meets system performance requirements.To do a feasibility study we need to consider the economic technical behavioral factors in the system development. First a project team is formed. The team develops system flowcharts that identify the characteristics of the system. The feasibility study is done on the basis of the following key questions like. What are the user’s demonstrable needs and how does the system meet them? What resources are available for giving systems? Is the problem worth solving? What are the likely impacts of the system on the organization?
The objective of the feasibility study is not to solve the problem but to acquire a sense of its scope. During the study the problem definition is crystallized and aspects of the problem to be included in the system are determined. The “Problem Statement” a carefully worded statement of the problem that led to analysis
4 | P a g e
summarize of finding and recommendation. A list of the major findings a quick access to the results of the analysis of the problem.
There are also some types of Feasibility Analysis listed below:
Economic feasibility
This is the most frequently used method for evaluating the effectiveness of a proposed system. More commonly known as cost-benefit analysis, the procedure is to determine the benefits and savings that are expected from the proposed system and compare them with costs. If benefits outweigh of the cost then the decision is made to design and implement the system. Otherwise further justifications or alternations in the proposed system will have to be made if it is to have a chance of being approved. This is an ongoing effort that improves in accuracy at each face of the system life cycle.
Technical feasibility
This centers on the existing computer system and to what extent it can support the proposed addition. This involves financial considerations to accommodate technical enhancement. If budget becomes serious constraint then the project is not feasible.
Behavioral feasibility 5 | P a g e
People are inherently resistant to change and computers have been known to facilitate change. An estimate should be made of how strong a reaction the user staff is likely to have toward the development of a system. Therefore this is clear that the system requires special effort to educate sell and train the staff. Thus we see that our propose system is technically, operationally and economically feasible.
Software Engineering Paradigm
Software engineering is the application of systematic, disciplined, quantifiable approach to the development, operation and maintenance of software that is the application of engineering to software.
To solve the actual problem in an industry setting a Software Engineer must incorporate a development strategy that enhances the process, method and tools layer. This strategy is often referred to as a process model or Software Engineering paradigm. A process model of Software Engineering is chosen based on the nature of project application.
It is clear that current state of software leaves much to be desired. A primary reason for is that, approaches to software development are frequently ad-hoc and programming centered. The ad-hoc or programming centered approach may work for small project, but for problem domain that we are interested in these approaches generally do not work. If we have to
6 | P a g e
control this software crisis, some methodical approach is needed for software development.
A definition of the software engineering from the economic and human perspective is given by Boehm (BoeSI) by combining the dictionary’s definition of engineering with its definition software.
His definition states:-“Software engineering is the application of science and mathematics by which the capabilities of computer equipment are made useful to man via computer programs, procedures and associated documents”.DATA FLOW DIAGRAM (DFD)
Demacro & Jane (1978) and Sarcon (1979) introduced Data Flow Diagram (DFD) and it is important to system analysis. DFD’s are very useful understanding a system and it can effectively used for partitions during analysis. A DFD shows the flow of data through a system. The system may be an organization, a manual procedure, a software system, mechanical systems, a hardware system, or any condition of these.
A DFD shows the movement of data through the different transactions or process in the systems. As the first step, an entire system can be depicted by one DFD, which gives a system overview it is called Context Diagram.
Data Flow Diagram (DFD) is a way of expressing system requirements in a graphical form. A DFD also known as bubble chart has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design.
7 | P a g e
Data Flow Diagram (DFD) symbols:
8 | P a g e
Square represents source or destination of System data also called an external entity
Arrow represents Data flow
Circle or Bobble represents a process that transform data from one form to another by performing some task with the data called process
Data Flow Diagram (DFD)
9 | P a g e
An Open Rectangle is a data store. Data store is a place where data is held temporarily from one transaction to the next or is stored permanently
This represents the Data Source
LEVEL -0 DFD (CONTEXT LEVEL DIAGRAM)
10 | P a g e
LEVEL-1 DFD
11 | P a g e
LEVEL 2 DFD
12 | P a g e
LEVEL2 DFD
13 | P a g e
Entity-Relationship Diagram:
An entity-relationship model (ERM) in software engineering is an abstract and conceptual representation of data. Entity-relationship modeling is a relational schema database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often a relational database, and its requirements in a top-down fashion.
Diagrams created using this process are called entity-relationship diagrams, or ER diagrams or ERDs for short. The definitive reference for entity relationship
14 | P a g e
modeling is generally given as Peter Chen's 1976. However, variants of the idea existed previously (see for example A.P.G. Brown) and have been devised subsequently.
The three main components of an ERD are:
The entity is a person, object, place or event for which data is collected. For example, if you consider the information system for a business, entities would include not only customers, but the customer's address, and orders as well. The entity is represented by a rectangle and labeled with a singular noun.
The relationship is the interaction between the entities. In the example above, the customer places an order, so the word "places" defines the relationship between that instance of a customer and the order or orders that they place. A relationship may be represented by a diamond shape, or more simply, by the line connecting the entities. In either case, verbs are used to label the relationships.
The cardinality defines the relationship between the entities in terms of numbers. An entity may be optional: for example, a sales rep could have no customers or could have one or many customers; or mandatory: for example, there must be at least one product listed in an order. There are several different types of cardinality notation; crow's foot notation, used here, is a common one. In crow's foot notation, a single bar indicates one, a double bar indicates one and only one (for example, a single instance of a product can only be stored in one warehouse), a circle indicates zero, and a crow's foot indicates many. The three main cardinal relationships are: one-to-one, expressed
15 | P a g e
as 1:1; one-to-many, expressed as 1:M; and many-to-many, expressed as M:N.
AN ENTITY RELATIONSHIP DIAGRAM METHODOLOGY: (One way of doing it)
1. Identify Entities
Identify the roles, events, locations, tangible things or concepts about which the end-users want to store data.
2. Find Relationships
Find the natural associations between pairs of entities using a relationship matrix.
3. Draw Rough ERD
Put entities in rectangles and relationships on line segments connecting the entities.
4. Filling Cardinality
Determine the number of occurrences of one entity for a single occurrence of the related entity.
5. Define Primary Keys
Identify the data attribute(s) that uniquely identify one and only one occurrence of each entity.
16 | P a g e
6. Draw Key-Based ERD
Eliminate Many-to-Many relationships and include primary and foreign keys in each entity.
7. Identify Attributes
Name the information details (fields) which are essential to the system under development.
8. Map Attributes
For each attribute, match it with exactly one entity that it describes.
9. Draw fully attributed ERD
Adjust the ERD from step 6 to account for entities or relationships discovered in step 8.
10. Check Results
Does the final Entity Relationship Diagram accurately depict the system data?
Project Snapshots
17 | P a g e
Login Page
18 | P a g e
Main Page
19 | P a g e
Servicing Page:
20 | P a g e
Cost Estimate Page:
21 | P a g e
Sales page:
22 | P a g e
Manager Page
23 | P a g e
Manager Page Showing Employee:
24 | P a g e
Update Servicing:
25 | P a g e
Show Update:
26 | P a g e
Employee Page
27 | P a g e
About Us:
Table Snapshots
Mobile Servicing Table
28 | P a g e
Customer Sales Table:
Sales Details
29 | P a g e
Employee Table:
Login Page Table:
30 | P a g e
Testing
Testing a program consists of subjecting the program to a set of test inputs and observing if the program behaves as expected then the condition under which failure occurs are noted for letter debugging and correction.
Testing Principals -
All tests should be traceable to customer requirements.
Testing Schedule: An overall testing schedule and resource planning must be made well in advance.
The Pareto principle implies that 80% of all errors uncovered during testing will likely be traceable to 20% of program modules.
31 | P a g e
Testing scheduling begins “in small “ and progress towards testing “in the large”
Exhaustive testing is not possible for any system.
To be most effective an independent third party should conduct testing.
Types of Testing -
White box testing Black box testing Interface testing
In “MOBILE SHOP MANAGEMENT SYSTEM” white box testing has been implemented which is concerned with the implementation of the program .The purpose is to exercise or try out different programming and database used in the program. The test concentrates on the examination of the code rather than the specification (which is left for black box testing).
32 | P a g e
References
1.Professional C# 2005 with .NET 3.02.C# 2005 Programming Black Book3.csharpcorner.com4.msdn.microsoft.com
33 | P a g e
Conclusion
This software has been made keeping it in mind that software is made for end users, not for programmers. So user friendliness keeping eye candy was first in the list. Wish this Student Admission System will serve satisfactory for which it is made. Easiness of mastering the whole process – with the use of Microsoft® Visual Studio® 2005 Visual C#.NET® and Microsoft® SQL Server® 2005 the process of controlling the whole system would be much easier and those can keep full control on the overall process without facing much trouble. With the user friendly GUI the software is very much user friendly and would be easy to use for anybody with a meager computer knowledge.
