Web Application Sample BB

A
PROJECT REPORT
ON
MOTIBA MANAGEMENT SYSTEM

DESIGNED AND DEVELOPED
BY
DARSHAN B. HINGU
SNEHA B. MEHTA
THIRD YEAR BACHELOR OF SCIENCE
(INFORMATION TECNOLOGY)
UNDER THE GUIDANCE OF

Ms. ANISHA ASIRVATHAM
DEPARTMENT OF INFORMATION TECNOLOGY
NAGINDAS KHANDWALA COLLEGE OF ARTS, COMMERCE &

MANAGEMENT STUDIES AND SHANTABEN NAGINDAS
KHANDWALA COLLEGE OF SCIENCE
MALAD (W) – 400 064
UNIVERSITY OF MUMBAI
(2015 – 2016)
MALAD KANDIVALI EDUCATION SOCIETY’S
NAGINDAS KHANDWALA COLLEGE OF COMMERCE, ARTS & MANAGEMENT

STUDIES & SHANTABEN NAGINDAS KHANDWALA COLLEGE OF SCIENCE
MALAD [W], MUMBAI – 64
(Reaccredited ‘A’ Grade by NAAC)
(AFFILIATED TO UNIVERSITY OF MUMBAI)
(ISO 9001:2008)
CERTIFICATE
This is to certify that,
DARSHAN B.HINGU
SNEHA B. MEHTA
Exam Seat No: 1057143

Exam Seat No: 1057062
Student of “Bachelor of Science (Information Technology) from “NagindasKhandwala

College, Malad(W)” has successfully completed and submitted the
PROJECTREPORT(USIT607)in partial fulfillment as per the syllabus prescribed by the
University of Mumbai during the academic year 2015-2016.
Project Guide Coordinator External Examiner
(B.Sc.IT/CS)
ACKNOWLEDGEMENT
I take this opportunity to express my gratitude to management of

NagindasKhandwala College for giving me this opportunity to accomplish this project work.
I am very thankful to Mrs. Ancy Jose, The Principal of NagindasKhandwala
College for her kind co-operation in the completion of our project.
A special thanks to our project guide Ms. AnishaAsirvatham for her most sincere efforts,
support and encouraging contribution throughout the project.
Also a great thank you to Mrs. Sindhu P.M. for supporting and encouraging us to
complete our project.
Last but not the least, I would like to thank all our friends & our family for their
support, motivation and encouragement.
( Sneha B. Mehta )
( Darshan B. Hingu )
Index
Sr. Contents Pg. No
No
1 ANALYSIS PHASE 1-13
1.1 Requirement Gathering Phase 1-2

1.1.1 Problem Statement 1
1.1.2 Fact Finding Techniques 1
1.1.3 Project Objective and Scope of Project 2
1.1.4 Problems with Existing System 2
1.1.5 Advantages of Proposed System 2
1.2 Feasibility Study 3-10

1.2.1 Operational Feasibility 3
1.2.2 Technical Feasibility 3
1.2.3 Economic Feasibility 4
1.2.4 Cost Benefit Analysis 5-9
1.2.4.1 COCOMO Model1 5
1.2.4.2 Function Point 8
1.2.5 Gantt Chart 10
1.3 Requirement Specification 11-12

1.3.1 Functional Requirement 11
1.3.2 Technical Requirement 11
1.3.3 Software Requirement Specification 12
1.4 Tools and Technology 13
2 DESIGN PHASE 14-32
2.1 Detailed Life Cycle of Project 14-23

2.1.1 Event Table 14
2.1.2 E-R Diagram 15
2.1.3 Use Case Diagram 16
2.1.4 Class Diagram 17
2.1.5 Activity Diagram 18
2.1.6 Sequence Diagram 19
2.1.7 State Machine Diagram 20
2.1.8 Component Diagram 21
2.1.9 Deployment Chart 22
2.1.10 Site Map 23
2.2 Physical Design 24
2.2.1 System Flow Chart 24
3 IMPLEMENTATION PHASE 25-48
3.1 Screen Layout 25-39

3.2 Report Layout 40-41
3.3 Validations 42
3.4 Test Cases 43-48
4 MAINTAINENCE AND EVALUATION 49-50
4.1 System Maintenance and Future Enhancement 49

4.2 User Manual 50
5 ANNEXTURE 51
5.1 References 51
5.2 Bibliography 51
1. ANALYSIS PHASE
1.1 Requirement Gathering Phase
1.1.1 Problem Statement
 Currently the client is making bills on paper.

 The main problem client facing is more time in writing the bills and to maintain the
records.
 In case of physical handlingof bill there is always possibility of bills getting
misplaced or being damaged which leaves the admin and client with no records
1.1.2 Fact Finding Technique
Q. How do you make invoice currently?

Attending the client face to face and making bills by writing on paper i.e.
physically.
Q. How much of your time is utilized in writing invoice daily?

Approximately 30% of the time goes in writing invoice.
Q. How much of time and efforts goes into maintaining and retrieving records?
Approximately 65% of time goes into maintaining and retrieving records.
Q. What are the problems you face?

 Writing physically.
 Time consuming.
 Occupies space in maintaining records.
 Records sometimes gets misplaced or damaged.
 Client sometimes suffers due to non-availability.
 Stationery cost.
Q. What are the results you expect?

A system/application which is less time consuming, saves space, provides
information at a click, reliable and useful.
Motiba Management System Page | 1

1.1.3 Objective and scope of the project
Motiba Management Systemwhich sets up to create an invoice, challan, credit notes,
debit notes, etc.This application allows admin to make invoice for multiple clients at a
time. This will help admin in not maintaining the records/history physically which
will save the time.
1.1.4 Problems with existing system

Currently the admin is making the bills and challanson paper. The main problem
admin is facing is that more time is consumed for writing invoices for multiple
clients. In case of physical invoices there is always possibility of invoices getting
misplaced or being damaged which leaves the admin and clients with no records
history.
1.1.5 Advantages of the proposed system

 This applicationis fast, easy & secure way to create and maintain the records.
 There is better performance in this application because the admin can login
from anywhere and it depends on speed of internet connection.
 The application maintains the history of the clients and all types of bill.
 Application will save the time and space of the admin.
 The stationery cost of the admin will be saved.

1.2 Feasibility Study
1.2.1 Operational feasibility
 Operational feasibility is to gain an understanding of whether the proposed

system willlikely to solve the business problems, or take advantage of the
opportunities or not. It is important to understand how the new system will fit the
current day-to-day operationsof the organization.
 We have also conducted an operational feasibility of our system to identify
whetherour system is able to satisfy the goal of developing the system.
 The other major requirement of Motiba Management Systemfor which we
wanted to develop application is for growth of business. This requirement was
also satisfied.
 The next thing was to make a solution to get the invoice details of previous time
of the clients. This problem was also solved.
 The next thing application needed was a system that is easy to use. So we
designed an interface which is extremely easy to use and also we have given
attention to application wherein admin can access the application from any
device.
1.2.2 Technical feasibility
 Assessing technical feasibility is to evaluate whether the new system will

performadequately and whether an organization has ability to construct a
proposed system ornot. The technical assessment help answer the question such
as whether the technologyneeded for the system exists, how difficult it will be to
build, and whether the firm hasenough experience using that technology.
 In case of technical feasibility, we have made a system that match according to
therequirements of the Motiba Management System.
 We have made the project in a language in which we are familiar. The entire
projectand website is made in Microsoft Visual Studio 2013 and SQL server
2014. We have chosen these to as the project issmall and also we are familiar
with the technologies.
 The next area where have concentrated is the operating system architecture.the
application can work in any operating system as its web based application So in
order to solve this problem we have made the software operating system and
architecture friendly.

1.2.3 Economic feasibility
 Economic evaluation is a vital part of investment appraisal, dealing with factors

thatcan be quantified, measured, and compared in monetary terms. The resultsof an
economic evaluation are considered with other aspects to make the projectinvestment
decision as the proper investment appraisal helps to ensure that the rightproject is
undertaken in a manner that gives it the best chances of success.
 The system according to us is cost effective as this a small group which is
containingonly two members working on this project.
 Since the time given to us almost 6 months we have more time and therefore less
manpower is required to develop the project.

1.2.4 Cost Benefit Analysis:
1.2.4.1 COCOMO Model 1:
COCOMO'81 models depends on the two main equations

1. Development effort: MM = a * KDSIb based on MM - man-month / person month /
staff-month is one month of effort by one person. In COCOMO'81, there are 152
hours per Person month. According to organization this values may differ from the
standard by 10% to 20%.
2. effort and development time (TDEV): TDEV = 2.5 * MMc
The coefficients a, b and c depend on the mode of the development. There are three
modes of development:
Development Project Characteristics

Mode Size Innovation Deadline/Constraint Dev.Environment
Organic Small Little Not light Stable
Semi-detached Medium Medium Medium Medium
Embedded Large Greater Tight Complex hardware/
customer interfaces
Basic COCOMO
The basic COCOMO applies the parameterized equation without much detailed
consideration of project characteristics.
Basic COCOMO a b C
Organic 2.4 1.05 0.38
Semi-detached 3.0 1.12 0.32
Embedded 3.6 1.20 0.32
MM = a * KDSIb
TDEV = 2.5 * MMc

Intermediate COCOMO
Basic equation for the model is used, but fifteen cost drivers are rated on a scale of 'very
low' to 'very high' to calculate the specific effort multiplier and each of them returns an
adjustment factor which multiplied yields in the total EAF (Effort Adjustment Factor).
EAF
Category Cost Driver Very Low Nominal High Very Extra
Low High High
Product RELY Required Software 0.75 0.88 1.00 1.15 1.40 -
Attributes Reliability
DATA Database Size - 0.94 1.00 1.08 1.16 -
CPLX Product Complexity 0.70 0.85 1.00 1.15 1.30 1.65
Computer TIME Execution Time - - 1.00 1.11 1.30 1.66
Attributes Constraint
STOR Main Storage - - 1.00 1.06 1.21 1.56
Constraint
VIRT Virtual Machine - 0.87 1.00 1.15 1.30 -
Volatility
TURN Computer - 0.87 1.00 1.07 1.15 -
Turnaround Time
Personnel ACAP Analyst Capability 1.46 1.19 1.00 0.96 0.71 -
Attributes AEXP Applications 1.29 1.13 1.00 0.91 0.82 -
Experience
PCAP Programmer 1.42 1.17 1.00 0.86 0.70 -
Capability
VEXP Virtual Machine 1.21 1.10 1.00 0.90 - -
Experience
LEXP Language 1.14 1.07 1.00 0.95 - -
Experience
Project MODP Modern 1.24 1.10 1.00 0.91 0.82 -
Attributes Programming Practices
TOOL Use of Software 1.24 1.10 1.00 0.91 0.83 -
Tools
SCED Required 1.23 1.08 1.00 1.04 1.10 -
Development Schedule

Basic COCOMO A b C
Organic 2.4 1.05 0.38
Semi-detached 3.0 1.12 0.32
Embedded 3.6 1.20 0.32
MM=a * KDSIb*EAF
TDEV = 2.2 * MMc
KDSI=5.5, a=3.0, b=1.12, c=0.35
EAF=1*1.08*1.15*1*1.07*1.0*0.91*0.86*0.95
= 0.988
MM=3*5.51.12*0.988
= 20.00
TDEV = 2.5*20.000.35
=2.5*2.85
=7.125

1.2.4.2 Function points:
Software Complexity Level Total

System CFP
Compon SIMPLE AVERAGE COMPLEX
ents
Count Weight Point Count Weight Point Count Weight Point
A Factor B C=A*B D Factor E F=D*E G Factor H I=G*
H
User Input 5 3 15 15 4 60 - 6 - 75
User Output 4 4 16 1 5 5 2 7 14 35
User 23 3 69 - 4 - - 6 - 69
Online
Queries
Logical Files 1 7 7 2 10 20 2 15 30 57
External - 5 - - 7 - - 10 - -
Files
Total 107 85 44 236
CFP
CALCULATION OF RCAF
• Summarizes the complexity characteristics of the software system

Assign grades(0 to 5) to the 4 subjects that substantially affect the
development effort
RCAF=
• The RCAF determines the technical complexity factor TCF = 0.65+0.01*RCAF
• FP = CFP*TCF

Sr.No Subject Grade
1 Requirement for reliable backup and recovery 3
2 Requirement for data communication 3
3 Extent of distributed processing 3
4 Performance requirements 5
5 Expected operational environment 4
6 Extent of online data entries 3
7 Extent of multi-screen or multi-operation online data input 1
8 Extent of online updating of master files 0
9 Extent of complex inputs, outputs, online queries and files 3
10 Extent of complex data processing 3
11 Extent that currently developed code can be designed for reuse 4
12 Extent of conversion and installation included in the design 4
13 Extent of multiple installations in an organization and variety of 0
customer organizations
14 Extent of change and focus on ease of use 4
Total = RCAF 40
Calculating FP
FP = CFP*TCF
TCF = 0.65+0.01*40
TCF= 1.05
FP=236*1.05
= 247.8

1.2.4 Gantt Chart

1.3 Requirement Specification
1.3.1 Functional Requirements

The application that we are making has the following functional requirement:
 Functions of Software:
 Creating & maintaining invoices.
 Creating & maintaining challans.
 Creating & maintaining Ledger.
 Creating & maintaining credit &debit notes.
 Creating & maintaining Quotation.
 Handling multiple clients.
 Backup and Restore facility.
 Adding & maintaining Products.
1.3.2 Technical Requirements
• For running software there is some specification and only if it satisfies the specified
requirement it will get installed and works as it is designed for.
• A technical requirement pertains to the technical aspects that your system must
fulfill, such as performance-related issues, reliability issues, and availability issues.
These types of requirements are often called quality of service (QoS) requirements,
service level requirements or non-functional requirements.
• For our software also there are some specification there are as follows:
 Minimum space required in HDD is 200MB.

 RAM required is 1GB.
 Screen resolution should be 1024x768 or more.
 Internet Connection.
 Web browser with latest version or any version that is not old than a year.
 Pen drive or external HDD for safe backup.
 Windows 7, 8.1 or any higher version.
 Works with both 32bit and 64bit Operating System.
 Microsoft .Net 4.0 and above.
The software will work properly as intended and smoothly only if the
requirements are met or else the software will work but it may lag.

1.3.3 Software Requirements specification
The Motiba Management System software is designed with the aim of creating and
maintaining Bills faster and easier.
 The software is capable of creating multiple bills and maintaining different clients.
 The software will have a login that keeps track that no one can use this application.
 Doctor Functionality:
 Add clients.
 Add products.
 User management.
 Add, view invoices.
 View clients history and number of invoice.
 Backup and Restore data.
 Print data.
 The software also has backup and recovery options to protect the data. This would
help to recover from any type of software or OS or any other failures.
As per the requirement and guidelines that you have given we have formulated this
document and by signing this document you accept that all the requirements are met. Any
change request hereafter will be chargeable as per the requirement.

1.4 Tools and Technology
The tools that we are using for this software are:

• Microsoft Visual Studio 2013.
• Microsoft SQL Server 2014.
• Microsoft Visual Studio 2013:

 Microsoft Visual Studio is an integrated development environment (IDE)
from Microsoft. It is used to develop computer programs for Microsoft
Windows, as well as web sites, web applications and web services. Visual
Studio uses Microsoft software development platforms such as Windows
API, Windows Forms, Windows Presentation Foundation, Windows Store
and Microsoft Silverlight. It can produce both native code and managed
code.
• Microsoft SQL Server 2014:
 Microsoft SQL Server is a relational database management system

developed by Microsoft. As a database, it is a software product whose
primary function is to store and retrieve data as requested by other software
applications, be it those on the same computer or those running on another
computer across a network (including the Internet).
 Microsoft SQL is playing an extremely important part in storing data.
Technologies that we have used in our project are as follows:
• SQL
• C#
• SQL:
 SQL (Structured Query Language) is a special-purpose programming

language designed for managing data held in a relational database
management system (RDBMS), or for stream processing in a relational data
stream management system (RDSMS).
 SQL plays an important role in saving retrieving and performing many
other operation for retrieving data from Microsoft SQL Server.
• C#:
 C# is a multi-paradigm programming language encompassing strong

typing, imperative, declarative, functional, generic, object-oriented, and
component oriented programming disciplines. It was developed by
Microsoft within its .NET. C# is intended to be a simple, modern,
general-purpose, object oriented programming language.

2.DESIGN PHASE
2.1 Detailed life cycle of project
2.1.1 Event table
Sr.No. Event Trigger Source Activity Response Destination
1 Admin Login Admin Checks for Opens Admin
Login valid username account if
and password successful
2 Admin Logout Admin Logs out of The Admin

Logout application application is
Navigate to
home
3 Add Entering Admin Adding new New Admin
Clients Clients Clients to Client gets
details application added
4 Edit Entering Admin Editing Client get Admin

Clients Clients Clients in edited
details application
5 Edit Editing Admin Editing Admin Admin Admin

Admin Admin details in details get
details application edited
6 Add Add Admin Adding New New Product Admin
Products Product Products to gets added
Details application
7 Edit Edit Admin Edited Edit Admin

Product Product Products to Product gets
Details application added
8 Add /Edit Add /Edit Admin Adding New Admin
Quotation Quotation /Editing New Quotation
Details Quotation Added/Edited
9 Add/Edit Add/Edit Admin Adding New Challan Admin
challan Challan Editing Added/Edited
Chalan
10 Add/Edit Add/Edit Admin Adding New Admin
Credit/Debit Credit/Debit /Editing Credit/Debit
Note Note Credit/Debit Note
Note Added/Edited
11 Add/Edit Add/Edit Admin Adding/Editing New Ledger Admin
Ledger Ledger Ledger Details details
Details Added/Edited
12 Add/Edit Add/Edit Admin Adding/Editing New Invoice Admin
Invoice Invoice Invoice Details details
Details Added/Edited

2.1.2 ER-Diagram
Figure: ER diagram

2.1.3 Use Case Diagram
Figure: Use Case Diagram

2.1.4 Class Diagram
Figure: Class Diagram

2.1.5 Activity Diagram
Figure: Activity Diagram

2.1.6 Sequence Diagram
Figure: Sequence Diagram

2.1.7 State Machine Diagram
Figure: State Machine Diagram

2.1.8 Component Diagram
Figure: Component Diagram

2.1.9 Deployment Chart
Web Application
Admin
Database Server
Figure: Deployment Diagram

2.1.10 Site Map
Figure: Sitemap

2.2.1 System flow chart
START
LOGIN
NO
If Valid
YES
Add/Edit/Delete
Client/Product/Quotation/Invoice/Chalan/Excis
e Invoice/Ledger/Profoma /Credit Notes/Debit
Notes
Print All Invoice
Save Reports
END
Figure: Flow chart

3. IMPLEMENTATION
PHASE
3.1 Screen Layout
 Login Page
Motiba Management
System

 Login Failure
Motiba Management
System

 Admin Homepage

 Add Buyer

 View Buyers
 Edit / Delete Buyers

 Add Product

 View Products

 Add Challan

 Add Excise Invoice

 Excise Invoice

 Add Quotation

 Quotation

 Add Proforma Invoice

 Add New Invoice

 Txa Invoice

3.2 Report Layouts
 Ledger Report

 Quotation Report

 Change User id

3.4 Test Cases
Black Box Testing:
Technique: Boundary Value Analysis (BVA)
Form: Add clients
Sr. No Test Case Input Excepted Actual Result

Output output
1 Enter Name Darshan It should It accepted Pass
accept
2 Enter Address1 Kandivali S.V It should It accepted Pass
Road accept
3 Enter Address2 Charkop Sector 6 It should It accepted Pass
accept
4 Enter C.E Regn Darshan123 It should not It did not Pass
No. accept accepted
5 Enter ECC No. 565Senha It should not It did not Pass
accept accepted
6 Enter Phone 8882634523 It should It accepted Pass
number accept
For Product:
Sr. No Test Case Input Excepted Output Actual output Result
1 Add Gift Frame It Should Accept It Accepted Pass

Product
2 Add Printed bottle It Should Accept It Accepted Pass
Product
3 Product Size:5/2 It Should Accept It Accepted Pass

description Color:Black
4 Price 123s It Should Not It did not pass

Accept accepted

User Management:
Sr. Test Case Input Excepted Actual Result

No Output Output
1 Change 90299d It Should Password Pass
Password Change the Changed
password
2 Forget Hingudarshan9@gmail.com It Should send Email Sent Pass
Password Email
Chalan:
Sr. Test Case Input Expected Actual Output Result
No Output
1 Select Buyer RedMoments It Should It Accept Pass
Accept
2 Chalan No. 189a It Should Not It Did Not Pass
Accept Accepted
3 Chalan Date 19/2/2016 It Should It Accepted Pass
Accept
4 Address Kandivali S.V It Should It Accept Pass
Road Accept
5 Order No. 9898 It Should It Accept Pass
Accept
Credit Notes:
Sr. Test Case Input Expected Actual Output Result

No Output
Accept
2 Credit No. 189a It Should Not It Did Not Pass
Accept Accepted
3 Credit Date 19/2/2016 It Should It Accepted Pass
Accept
Road Accept
5 Product Printed Bottle It Should It Accept Pass
Name. Accept
6 Rate One thousand It Should Not It Pass
Accept Did Not
Accepted

Debit Note:
Sr. Test Case Input Expected Actual Result
No Output Output
Accept
2 Credit No. 189a It Should Not It Did Not Pass
Accept Accepted
3 Credit Date 19/2/2016 It Should It Accepted Pass
Accept
Road Accept
Name. Accept
6 Rate One thousand It Should Not It Pass
Accept Did Not
Accepted
Excise Invoice:

No Output Output
Accept
2 Invoice No. 189v It Should Not It Did Not Pass
Accept Accepted
3 InvoiceDate 11/2/2016 It Should It Accepted Pass
Accept
4 Address CharkopS.V It Should It Accept Pass
Road Accept
5 Product Name. Printed Bottle It Should It Accept Pass
Accept
6 Page No. D123 It Should Not It Pass
Accept Did Not
Accepted
Ledger:

No Output Output
Accept
2 Amount 189Rs It Should Not It Did Not Pass
Accept Accepted
3 Invoice Date 11/2/2016 It Should It Accepted Pass
Accept

Tax Invoice:

No Output Output
Accept
2 Invoice No. 200e It Should Not It Did Not Pass
Accept Accepted
3 Invoice Date 11/2/2014 It Should It Accepted Pass
Accept
4 Address Malad SV It Should It Accept Pass
Road Accept
Name. Accept
6 Quntity D123 It Should Not It Pass
Accept Did Not
Accepted

White Box Testing:
Technique: Cyclomatic Complexity
Form: Doctor Sign up
Cyclomatic Complexity=E-N+P
Where,
E=number of edges in the flow graph.
N=number of nodes in the flow graph.
P=number of nodes that have exit points.
Cyclomatic Complexity for user validate function.
Here, E=36, N=35, p=2
Therefore,cyclomatic complexity = 36-35+2 = 3
Complexity=3
Path coverage:
Basic paths to be tested
Path 1: 1-2-3-4-5-33-34
Path 2: 1-2-6-7-8-9-33-34
Path 3: 1-2-3-4-5-6-7-8-9-10-11-12-13-14-15-18-19-20-21-22-23-24-25-26-27-28-29-30-
31-32-33-34

Therefore, path coverage=3
Figure: Control Flow Diagram/Graph

4. MAINTENANCE
AND
EVALUATION
4.1System maintenance and future enhancement
System Maintenance:
Once the software is delivered and deployed, then maintenance phase starts. Software
requires maintenance because there are some residual errors remaining in the system that
must be removed as they are discovered.
They have taken annual contract to us for regular software check-ups.
In Maintenance we will be doing the following:
• Fixing bugs if at all anything found during actual working.

• Any minor changes that is required when the client working with it will be done.
• Periodic checking of software at regular intervals.
• Make better use of existing tools and techniques.
• Online technical support at any instance of time.
Future Enhancement:
Nothing can be ended in a single step. It is the fact that nothing is permanent in this world.
So this project also has some future enhancements in the evergreen and booming IT
industry.
Further enhancement of the software will have the following features:
• Customized Tally will be incorporated which will keep track of all the expense,
income obtained each month and many more.
• Alerts the clients when bill is generated for a month via SMS and e-mail. Also will
be having remainder alerts.
• A web application will be developed that will make bill and receipt generation faster
and on the go.
• Also apps for mobiles will be developed making things handy and portable.

4.2USER MANUAL:
Since this a customized software it is designed as per the user requirement and suggestions
most of the stuff are known to user.
Admin side:
How to do backup and restore?

1. Login to standalone using credentials.
2. There you will find backup and restore button.
3. Click on it and then your get two buttons one for backup and other one for restore.
4. Choose the one you want to do and then give the file path and press the backup
button for backup and restore button if you are restoring.
Printing reports:
1. Login to standalone using credentials.
2. Now click on working with existing system and in that select the report for which
you want to print the report.
3. Now you will find print button click on it and select the month and year and then
click on print.
FAQ’s
For where do I get username and password?
Ans: You will get the credentials from the accountant using which you can login.
Can I view the web application in mobile?
Ans: It works perfect okay with mobile browser.

5.ANNEXTURE
5.1 References
Person:
 Mr. Jay B. Mehta
Videos:
 Programmingtoprogramming | The Complete Tutorial to Learn ASP.Net
Websites:
 www.tutorialspoint.com
 Stackoverflow.com
 www.W3School.com
5.2 Bibliography
 https://en.wikipedia.org
 http://www.W3School.com
 http://stackoverflow.com
 http://www.tutorialspoint.com
 https://www.youtube.com

Web Application Sample BB

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Web Application Sample BB

Загружено:

Авторское право:

Доступные форматы

A

MOTIBA MANAGEMENT SYSTEM

UNDER THE GUIDANCE OF

DEPARTMENT OF INFORMATION TECNOLOGY

NAGINDAS KHANDWALA COLLEGE OF ARTS, COMMERCE &

NAGINDAS KHANDWALA COLLEGE OF COMMERCE, ARTS & MANAGEMENT

This is to certify that,

Exam Seat No: 1057143

Student of “Bachelor of Science (Information Technology) from “NagindasKhandwala

Project Guide Coordinator External Examiner

I take this opportunity to express my gratitude to management of

1 ANALYSIS PHASE 1-13

1.1 Requirement Gathering Phase 1-2

1.2 Feasibility Study 3-10

1.3 Requirement Specification 11-12

1.4 Tools and Technology 13

2 DESIGN PHASE 14-32

2.1 Detailed Life Cycle of Project 14-23

3 IMPLEMENTATION PHASE 25-48

3.1 Screen Layout 25-39

4 MAINTAINENCE AND EVALUATION 49-50

4.1 System Maintenance and Future Enhancement 49

1.1.1 Problem Statement

 Currently the client is making bills on paper.

1.1.2 Fact Finding Technique

Q. How do you make invoice currently?

Q. How much of your time is utilized in writing invoice daily?

Q. What are the problems you face?

Q. What are the results you expect?

Motiba Management System Page | 1

1.1.4 Problems with existing system

1.1.5 Advantages of the proposed system

Motiba Management System Page | 2

1.2.1 Operational feasibility

 Operational feasibility is to gain an understanding of whether the proposed

1.2.2 Technical feasibility

 Assessing technical feasibility is to evaluate whether the new system will

Motiba Management System Page | 3

 Economic evaluation is a vital part of investment appraisal, dealing with factors

Motiba Management System Page | 4

1.2.4.1 COCOMO Model 1:

COCOMO'81 models depends on the two main equations

Development Project Characteristics

TDEV = 2.5 * MMc

Motiba Management System Page | 5

Motiba Management System Page | 6

TDEV = 2.2 * MMc

KDSI=5.5, a=3.0, b=1.12, c=0.35

Motiba Management System Page | 7

Software Complexity Level Total

• Summarizes the complexity characteristics of the software system

Motiba Management System Page | 8

Motiba Management System Page | 9

Motiba Management System Page | 10

1.3.1 Functional Requirements

1.3.2 Technical Requirements

 Minimum space required in HDD is 200MB.

Motiba Management System Page | 11

Motiba Management System Page | 12

The tools that we are using for this software are:

• Microsoft Visual Studio 2013:

 Microsoft SQL Server is a relational database management system

Technologies that we have used in our project are as follows: