Answer / monika

The waterfall model seems an ideal choice here. No other
model seems a reasonable alternative to accept as a
different answer.
Strengths:
1. The company is large and bureaucratic, requiring
documentation and good
project visibility. Waterfall documentation satisfies this.
2. The company has a high staff turnover. So probably many
employees are
new and inexperienced. Waterfall works well with
inexperienced staff.
3. The application type is well known to the company, so a
thorough user
requirements analysis should be possible early on.
4. An existing application is to be re-engineered. This also
confirms that the
user requirements are known early. They could be extracted
from the existing application.
5. The company will maintain the software, so good
documentation will be essential.
6. The company has a good reputation to maintain in this
area, so quality control will be essential. Waterfall
emphasis of requirements-before-design and
design-before-coding will emphasise quality.
Weaknesses:
Waterfall has no obvious weaknesses on this project.
1. We may end up swimming upstream, but the chances seem
minimal since the requirements should be clear from the start.
2. Late arrival of code may be one, but on the other hand
our client may be able to continue using the existing
application until the new system arrives.

Solution 1 (b) : Functional and Non-Functional requirements
Interface Requirement, This section defines the parameters
that the software product must follow while interacting with
the outside world.
User Interfaces :
1. Login Screen
2. Menu selection Screen
3.Employee Salary Details
4.Employee Loan Details
5.Employee Leave Details
6.Employee Tax Details
7.Generate Salary Slip
8.Employee Bank Details
Hardware Interfaces Server Configuration: Minimum 2GB Hard
Disk P-III processor or equivalent Ram 512 MB Windows with
Apache preloaded.Client Configuration: A terminal with
Internet Explorer and Printer.
Software Interfaces Operating system –
WindowsXP/2000Language -- JSPDatabase –
OracleNetwork -- LAN Communications Interfaces
Communications interfaces can be provided through email,web
browser, network server communications protocols, electronic
forms, and so on. For this we can use communication
standards such as FTP or HTTP to provide security using
encryption algorithms and synchronization mechanisms
Functional Requirements:
This section analyzes various angles of the functionality to
be developed. You do not need to use each type of analysis
for the entire system. Select only those analyses that best
allow you to complete your understanding of the
requirements. Feature Analysis The Automated Payroll
Processing system consists of following modules.Admin : In
this module admin is provided with many services such as
assigning roles, Add new employee, Update Salary Details,
Update Loan Details, Update Leave Details, Update Tax
Details, Generate Salary Slip, View employee
account.Employee: In this module employee is provided with
the services such as Update personal profile, Change
Password, View earnings, View Deductions, View Salary Slip.
Nonfunctional Requirements:
Performance Requirements System can withstand even though
many number of users requested the desired service. As we
are keeping office level server of the automated payroll
system. And access is given to the only registered users of
office who requires the services of viewing, Updating etc.
It can withstand the load Safety & Reliability Requirements
By incorporating a robust and proven SQL into the system,
reliable performance and integrity of data is ensured. There
must be a power backup for server system.
Security Requirements
Sensitive data is protected from unwanted access by users
appropriate technology and implementing strict user- access
criteria. Software Quality Attributes Menu-driven programs
with user friendly interface with simply hyper links. It is
very easy to use. Backup mechanisms are considered for
maintainability of software as well as database. As it is
object oriented reusability exists. As project is based on
MVC architecture, testability exists.

Solution 1(c)....Draw Gantt and Pert charts as per Project.

Solution 1 (d): Sample Costing for System .

Ratings

Very...................................................................
Very Extra

Cost Drivers

Low .......
Low......Nominal......................High....High ...High


Product attributes

Required software reliability.......... 0.75
......0.88.......1.00 ........................1.15
....1.40.......___

Size of application database
..........---...........0.94........1.00
.................1.08 ....1.16....___

Complexity of the product ......... 0.70........0.85
.......1.00.............1.15....1.30......1.65

Hardware attributes

Run-time performance...............
___.......___.........1.00
.......................1.11.....1.30.....1.66

Memory constraints
......................___.....___...........1.00
.....................1.06 ......1.21 ......1.56

Volatility of virtual machine

Environment .
...........................___.........0.87.......1.00..................1.15........
1.30.....___

Required turn about time............ ...___.........0.87
.... 1.00 .................1.07........ 1.15......___

Personnel attributes

Analyst capability .
............................1.46.......1.19......1.00.................0.86.......
0.71....___

Applications experience
...................1.29......1.13.......1.00
.......................0.91... 0.82...___

Software engineer capability ...........1.42
.....1.17.......1.00 ......................0.86.......
0.70...___

Virtual machine experience ............. 1.21......1.10
......1.00.......................0.90......___.......___

Programming lang
experience..........1.14......1.07.......1.00
..............0.95.....___........___

Project attributes

Use of software tools ...................1.24......1.10
......1.00...............0.91.......0.82.....___

Software engineering methods..........1.24 ....1.10
.....1.00..........091........... 0.83.....___

Required devlpmnt schedule.......1.23 ...1.08
......1.00....................1.04...... 1.10....___

The Intermediate Cocomo formula now takes the form:
E=ai(KLoC)(b)i.EAF where E is the effort applied in
person-months, KLoC is the estimated number of thousands of
delivered lines of code for the project, and EAF is the
factor calculated above. The coefficient ai and the exponent
bi are given in the next table.
Software project ai bi Organic 3.2 1.05
Semi-detached 3.0 1.12 Embedded 2.8 1.20

Solution 1(e) SRS for system Overview
The Software Requirements Specification (SRS) begins the
translation process that
converts the software requirements into the language the
developers will use. The SRS
draws on the use-cases from the User Requirement Document
(URD) and analyzes the
situations from a number of perspectives to discover and
eliminate inconsistencies,
ambiguities, and omissions before development progresses
significantly under
mistaken assumptions.
Problem Frame Machine Domain --- Automated Payroll Processing
Problem Domain --- Maintaining employee records, updating
profiles,updating loans References LBRCE –JKC. User
Requirements Document v.1.0.1 LBRCE – JKC High-Level Design
v.1.0.1 LBRCE – JKC Software Requirments Specifications v.1.0.1
Interface Requirements
This section defines the parameters that the software
product must follow while interacting with the outside world.
User Interfaces
1. Login Screen
2. Menu selection Screen
3. Employee Salary Details
4. Employee Loan Details
5. Employee Leave Details
6. Employee Tax Details
7. Generate Salary Slip
8. Employee Bank Details
Hardware Interfaces
Server Configuration:
Minimum 2GB Hard Disk
P-III processor or equivalent
Ram 512 MB
Windows with Apache preloaded.
Client Configuration:
A terminal with Internet Explorer and Printer.
Software Interfaces
Operating system – WindowsXP/2000
Language -- JSP
Database – Oracle
Network -- LAN
Communications Interfaces
Communications interfaces can be provided through e-mail,
web browser, network server communications protocols,
electronic forms, and so on. For this we can use
communication standards such as FTP or HTTP to provide
security using encryption algorithms and synchronization
mechanisms
Functional Requirements
This section analyzes various angles of the functionality to
be developed. You do not
need to use each type of analysis for the entire system.
Select only those analyses that
best allow you to complete your understanding of the
requirements. Feature Analysis The Automated Payroll
Processing system consists of following modules.
Admin :
In this module admin is provided with many services such as
assigning roles, Add new employee, Update Salary Details,
Update Loan Details, Update Leave Details, Update Tax
Details, Generate Salary Slip, View employee account.
Employee: In this module employee is provided with the
services such as Update personal profile, Change Password,
View earnings, View Deductions, View Salary Slip.
Nonfunctional Requirements
Performance Requirements
System can withstand even though many number of users
requested the desired service. As we are keeping office
level server of the automated payroll system. And access is
given to the only registered users of office who requires
the services of viewing, Updating etc. It can withstand the load
Safety & Reliability Requirements
By incorporating a robust and proven SQL into the system,
reliable performance and integrity of data is ensured. There
must be a power backup for server system.
Security Requirements
Sensitive data is protected from unwanted access by users
appropriate technology and implementing strict user- access
criteria.
Software Quality Attributes
Menu-driven programs with user friendly interface with
simply hyper links. It is very easy to use. Backup
mechanisms are considered for maintainability of software as
well as database. As it is object oriented reusability
exists. As project is based on MVC architecture, testability
exists.IMSF
Solution1(f) Develop Test Plan Document :
In a software development project, errors can be injected at
any stage during development. The development of software
involves a series of production activities where
opportunities for injection of human fallibilities are
enormous. Because of human inability to perform and
communicate with perfection, software development is
accomplished by a quality assurance activity. Testing is a
process which reveals errors in the program. It is the major
quality measure employed during software development. During
testing, the program is executed with a set of test cases
and the output of the program for the test cases is
evaluated to determine if the program is performing as it is
expected to perform.
Scope:
This document describes all the tests taking place for JKC
Release 1.0. It covers the design elements specified in the
OOD and the detailed modeling elements of the system being
tested. References User requirements document, Software
Requirements specification document. Detailed design
document. IMSF
Testing Objective:
Testing is a process of executing a program with the intent
of finding an error.A good test case is the one that has a
high probability of A successful test is one that finding an
as-yet undiscovered error. uncovers an as-yet undiscovered
error.
In order to make sure that the system does not have errors,
the different levels of testing strategies that are applied
at different stages of software development are:
_ Unit Testing.
_ System Testing.
Unit Testing:
Unit testing is done on individual modules as they are
completed and become executable. Unit testing treats each
component as stand-alone entity which does not need other
components during the testing process.
System Testing:
This involves in-house testing of the entire system before
delivery to the user. Its aim is to satisfy the user. The
system meets all the requirements of the client’s specification.
Results:-
Administrator module:
1. Test case : Login
Input : ID, Password.
Process : Click on the login link. If administrator enters
ID and password correct it goes to the admin services
otherwise displays the same page with an error message.
Output : Displays the admin services page.
2. Test case : Add new employee
Input : Name, Id, designation, Date of joining.
Process : A new employee can be added into the system and
admin can update his details.
Output : The employee can be credited salary based upon his
details.
3. Test case : Salary details
Input : Id, designation, basic salary, PF, DA, HRA.
Process : The admin can update his salary details
Output : Employee salary details will be updated to the
database.
4. Test case : Loan details
Input : Id, Loan number, EMI, Repaid amount, Balance amount.
Process : Administrator can update a particular employee’s
loan details.
Output : Employee Loan details will be updated to the database.
5. Test case : Leave details
Input : Id, Type of leave, Number of Leaves.
Process : Administrator updates the leave details.
Output : Employee Leave details will be updated to the database.
6. Test case : Tax details
Input : Id, Basic salary, Tax percentage, income tax.
Process : The tax details of an employee can be updated by
the administrator.
Output : Employee Tax details will be updated to the database.
7. Test case : Salary slip
Input : Id, Basic salary, Designation, Net pay.
Process : Based on the leave, loan , tax details the slip
will be generated
Output : Salary slip will be generated.
8. Test case : Bank details
Input : Id, Designation, salary
Process : The employee’s salary is credited to bank.
Output : Employee can View and receive the salary.
Employee module:
1. Test case : Login
Input : ID, Password.
Process : Click on the login link. If Employee enters ID and
password correct it goes to the other page otherwise
displays the same page with an error message.
Output : Displays the Information to be viewed by an employee
2. Test case : Update profile
Input : Id, Name, Designation, Email-id, Mobile number,
Address,key skills,qualification
Process : The employee can update his profile if any
modifications occur in his details
Output : The details of an employee can be updated
3. Test case : Change password
Input : Id, Old password, New password
Process : Employee can be able to change his password by
using this test case
Output : Employee new password will be updated
4. Test case : View earnings
Input : ID, Month, Year.
Process : The earnings can be displayed by this test case
Output : The total earnings of an employee for the specified
month and year can be viewed
5. Test case : View deductions
Input : Id, Month, Year
Process : The deductions can be known by using this test case
Output : The total deductions of an employee for the
specified month and year can be viewed
6. Test case : View salary slip
Input : Id, Month, Year.
Process : The employee can view the salary slip.
Output : The salary slip of an employee for the specified
month and year can be viewed.

Answer / munjalpankaj

Spiral Model, as this combines the elements of both design
and prototyping in stages, in an effort to combine
advantages of top-down and bottom-up concepts.

what is the different between all software models

0 Answers  

---

I am less than 6 feets tall but more than 2 feet taal. My height in inches is a multiple of 7 and is also 2 inches more than a multiple of 6. What is my height in inches?

1 Answers  

---

i am a student may i know mhat are the software companies providing industrial visit in chennai

0 Answers  

---

Q1. Write ten test cases on mm/dd/yy 1699<=YY<=1999

0 Answers   Adobe,

---

John weight twice as much as Marciua. Marcia weight is 60% of Bob's weight. Dave weight s 50% of lee weight 190% of john weight. Which of these 5 person weight the least?

1 Answers  

---

---

what is meant by business rules ?

0 Answers  

---

from delhi mohammed-bin-tughlak transferred his capital to

1 Answers  

---

dns is an acronym for

1 Answers  

---

what us software development life cycle explain briefly

3 Answers  

---

why we call water fall model as waterfall

3 Answers  

---

what is the defference between test specification and test plan?

0 Answers   Virtusa,

---

how to track the requirements if all ready it is available for that product

0 Answers   IBM,

---