You are on page 1of 39

Swarna Bharathi Institute Of science & Technology

PRODUCT MAINTENANCE SYSTEM

Guide name : Mr. D. Ramesh, Associate Professor

Project Team: 1) 07M61A0574 - V. Deepika 3) 07M61A0580 - M. Harish 2) 07M61A0575 - P. Deepthi 4) 07M61A05D0 - N.V.N.S. Sai Sailaja

Presentation Agenda
‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡

Introduction Requirement Analysis System Analysis System Design Testing I/O Screens Applications Future Scope Bibliography

Introduction :
‡ This project is aimed to developing an Online Product Maintenance System, used within manufacturing industry. ‡ The Product Maintenance System is a client server based application that can be accessed by a selected group of users. ‡ This system can be used for maintaining all the details related to a product like Product hierarchy, product/subcomponents attributes (cost/size/weight etc.) and supplier details. ‡ There are additional features like user access control, report generators etc in this system

8 GHz Processor and Above ‡ RAM 512MB and Above ‡ HDD 20 GB Hard Disk Space and Above .REQUIREMENTS ANALAYSIS: HARDWARE REQUIREMENTS: ‡ PIV 2.

SOFTWARE REQUIREMENTS: ‡WINDOWS OS (XP / 2000 / 200 Server / 2003 Server) ‡Visual Studio .0 (IIS) ‡Visual Studio .Net 2005 Enterprise Edition ‡Internet Information Server 5.Net Framework (Minimal for Deployment) ‡SQL Server 2000 Enterprise Edition .

.SYSTEM REQUIREMENT ANALYSIS: INTRODUCTION ‡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 other is to understand the requirements and domain of the new system. but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. ‡Both the activities are equally important.

improper understanding of present system can lead diversion from solution .‡Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult.

 First of all the feasibility study is done. .  If system exists one and modification and addition of new module is needed.PROBLEM ANALYSIS  The model that is basically being followed is the WATER FALL MODEL.  Once that part is over the requirement analysis and project planning begins. analysis of present system can be used as basic model. which states that the phases are organized in a linear order.

the testing is done.  In this model the sequence of activities performed in a software development project are: - 1) 2) 3) 4) 5) 6) 7) Requirement Analysis Project Planning System design Detail design Coding Unit testing System integration & testing . Once the programming is completed. The design starts after the requirement analysis is complete and the coding begins after the design is complete.

WATER FALL MODEL: Changed Requirements Communicated Requirements Requirements Specification Requirements Engineering Design Specification Design Executable Software Modules Programming Maintenance Integrated Software Product Process Integration Delivered Software Product Product Input Product Output Delivery .

once system requirement have been specified and analyzed.SYSTEM DESIGN  Software design sits at the technical kernel of the software engineering process and is applied regardless of the development paradigm and area of application. code and test that is required to build and verify software. . system design is the first of the three technical activities design.  The designer¶s goal is to produce a model or representation of an entity that will later be built.  Beginning.  Design is the first step in the development phase for any engineered product or system.

Design is the place where quality is fostered in software development. . one whose quality cannot be assessed until the last stage. Design provides us with representations of software that can assess for quality. Design is the only way that we can accurately translate a customer¶s view into a finished software product or system. Software design serves as a foundation for all the software engineering steps that follow. Without a strong design we risk building an unstable system ± one that will be difficult to test.The importance can be stated with a single word ³Quality´.

During design. progressive refinement of data structure. and procedural details are developed reviewed and documented. . program structure. From the technical point of view. design is comprised of four activities ± architectural design data structure design interface design procedural design. System design can be viewed from either technical or project management perspective.

USE CASE MODEL SYSTEM NAME Use case 1 Use case 2 Actor Actor Use case n .

Home Page Login Page Admin Home Page Add/Delete products Add/Delete Employee Search Employee Admin Search Products Set hierarchy to prod Generate Reports Send MailtoUsers ReporT Update Profile ChangePassword View all Products .

Register Employee Search for Employee Search for Status Search for Products Home Page Login Page Employee Home Page Add/Delete Supplier Add/Delete Family Add Class Employee Add Products Generate Report Enquiry about the Product Send Request to User Repor Update Profile ChangePassword View all Products .

E R DIAGRAMS .

ADMIN LOGIN SEQUENCE DIAGRAM Admin frmLogin Bal : clsLogin Dal : Sqlhelper DataBase 1 : lnkButton() 2 : btn_submit() 3 : Execute_NonQuery() 4 : Stored Database() 5 : Invalid() 6 : Go Back() .

EMPLOYEE LOGIN SEQUENCE DIAGRAM Employee frmLogin Bal : clsEmp Dal : Sqlhelper DataBase 1 : lnkButton() 2 : btn_submit() 3 : Execute_NonQuery() 4 : Stored Database() 5 : Invalid() 6 : Go Back() .

PRODUCT SEQUENCE DIAGRAM Admin frmProduct Bal : clsProduct Dal : sqlHelper DataBase 1 : lnkButton() 2 : InsertProduct() 3 : ExecuteNonquery() 4 : Stored DataBase() .

SUPPLIER SEQUENCE DIAGRAM Admin frmSupplier Bal : clsSupplier Dal : sqlHelper DataBase 1 : lnkButton() 2 : InsertSupplier() 3 : ExecuteNonquery() 4 : Stored DataBase() .

 In fact.TESTING :  Software testing is a critical element of software quality assurance and represents the ultimate review of specification. .  Testing is the set of activities that can be planned in advance and conducted systematically. design and coding. testing is the one step in the software engineering process that could be viewed as destructive rather than constructive.

UNIT TESTING MODULE TESTING Component Testing SUB-SYSTEM TESING Integration Testing SYSTEM TESTING ACCEPTANCE TESTING User Testing .

UNIT TESTING Unit testing focuses verification effort on the smallest unit of software design. the module. The unit testing we have is white box oriented and some modules the steps are conducted in parallel. WHITE BOX TESTING This type of testing ensures that ‡All independent paths have been exercised at least once ‡All logical decisions have been exercised on their true and false sides ‡All loops are executed at their boundaries and within their operational bounds .

we have created independently to verify that Data flow is correct.  To follow the concept of white box testing we have tested each form . All conditions are exercised to check their validity. All internal data structures have been exercised to assure their validity. All loops are executed on their boundaries .

SAMPLE SHOTS: .

.

.

.

.

.

.

.

‡There are checks on every stages of any new creation. The merits of this project are as follows: ‡It¶s a web-enabled project. whatever he is entering. ‡The user is mainly more concerned about the validity of the data.APPLICATIONS: The project is identified by the merits of the system offered to the user. . This is very helpful for the client to enter the desired information through so much simplicity. data entry or updation so that the user cannot enter the invalid data. ‡This project offers user to enter the data through simple and interactive forms. which can create problems at later date.

‡There are options for him by which he can update the records. . ‡User is provided the option of monitoring the records he entered earlier. Moreover there is restriction for his that he cannot change the primary data field.‡Sometimes the user finds in the later stages of using project that he needs to update some of the information that he entered earlier. He can see the desired records with the variety of options provided by him. This keeps the validity of the data to longer extent.

. increasing the load on the database back up and data maintenance activity. Training for simple computer operations is necessary for the users working on the system.LIMITATIONS: The size of the database increases day-by-day.

further the system may be utilized in various other types of auditing operation viz.FUTURE SCOPE:  This System being web-based and an undertaking of Cyber Security Division.. Network auditing or similar process/workflow based applications..  Moreover.  A console for the data centre may be made available to allow the personnel to monitor on the sites which were cleared for hosting during a particular period. . needs to be thoroughly tested to find out any security gaps. it is just a beginning.

BIBILOGRAPHY: Title Author Publication Title Author Publication Title Author Publication : Professional c#2008 : Simon Robinson . Pressman : Tata McGraw Hill Publications . Christian Nagel. A Practitioners Approach : Roger S. : Wrox Publication : Designing the User Interface : Ben Shneiderman : Addision Wesely Publications : Software Engineering.