IT 510 Final Project Guidelines and Rubric
Overview
The final project for this course is the creation of a System Proposal Document.
In any modern enterprise, it is crucial that all of the different stakeholders, users, inputs, and outputs that relate to the business’s IT systems coalesce in a logical
and cohesive way for the systems to be effective. As a member of an IT team, your overarching goal is to ensure that the IT systems ultimately do what the
business needs them to do. In this course, you have learned about the key principles and practices underlying the analysis, design, implementation, and
management of IT systems. In this final project, you will apply this knowledge by creating a systems proposal document.
The project is divided into four milestones, which will be submitted at various points throughout the course to scaffold learning and ensure quality final
submissions. These milestones will be submitted in Module Two, Module Four, Module Six, and Module Eight. The final submission will occur in Module Nine.
In this assignment, you will demonstrate your mastery of the following course outcomes:
Assess the relationship of systems analysis, design, implementation, and development processes as they relate to the management of information
technology systems
Communicate the paradigms, processes, and activities of systems development to diverse audiences
Apply structure and object oriented analysis modeling techniques to analyze, design, and manage information technology systems
Construct written and visual representations of the analysis, design, implementation, and management of information technology systems based on the
systems development life cycle
Prompt
You will select your own case study and will apply the content provided, describing the business process to complete the final project. Alternate sources for case
studies include the case studies found in the textbook with the exception of the Personal Trainer Case. You can additionally search the internet for business case
ideas.
You will complete an analysis of an existing information technology system and make recommendations for updates to meet business goals based on your chosen
case study. Your final submission will include an introduction, systems requirements, systems design specifications, and an implementation plan. All of the
components listed below should be submitted as a single, organized systems proposal document and include screenshots of all relevant diagrams, charts, and
tables.
I.
Introduction: Provide an overview of your selected case. Be sure to provide appropriate citations and reference to the case study you have selected.
a) Background: Establish a context for understanding your systems proposal. Specifically, explain any essential paradigms, processes, and activities
of the existing information technology systems.
b) Problem Statement: What is the problem that needs to be solved? Why is it a problem? What are the impacts to the enterprise?
c) Audience: Who are your audiences for this systems proposal? How will you effectively communicate the information of your proposal to these
diverse groups?
II. Systems Requirements: Detail the specific requirements of your case. Be sure to include screenshots of all relevant diagrams, charts, and tables.
a) Requirements Modeling: Assess the current system to identify the requirements for the new system. Be sure to address each of the following
aspects: outputs, inputs, processes, performance, and controls (i.e., security).
b) Data Process Model: Create a visual representation of all relevant data processes that represents a logical model of the requirements of the
system based on the systems development life cycle.
c) Data Flow Diagrams: Create a visual representation of the data flow based on the systems development life cycle.
d) Data Dictionary: Create a data dictionary that annotates your system requirements to build clarity in communicating with the relevant
audiences.
e) Object Modeling: Use appropriate object modeling techniques and tools to describe the system requirements.
f) Use Case Diagrams: Create (a) use case diagram(s) that outline the system requirements based on the systems development life cycle.
III. Systems Design: Propose a solution that addresses the identified problem in your case. Be sure to include screenshots of all relevant diagrams, charts,
and tables.
a) Specifications: Provide a physical design that will meet the specifications outlined in the systems requirement document.
b) Data Design: Create entity relationship diagrams that accurately describe the proposed solution, including 3NF table designs.
c) User Interface Design: Illustrate the user interface design. Specifically, be sure to address your proposed human computer interactions (HCIs) and
graphical user interfaces (GUIs). Your proposals should follow user-centered design principles and address all design requirements.
d) System Architecture: Describe the system architecture. Specifically, be sure to address the corporate organization and culture, enterprise
resource planning, total cost of ownership, scalability, integration and interface requirements, and security.
e) Feasibility Analysis: Provide supporting details that justify why your proposed solution is appropriate for solving the problem. In your defense,
be sure to address operational, technical, economic, and scheduling feasibility. Be sure that you frame your response for communicating
effectively to your target audiences.
IV. Project Plan: Illustrate your recommended implementation and management strategies. Be sure to include screenshots of all relevant diagrams, charts,
and tables.
a) Work Breakdown Structure: Describe all of the essential roles and functions required for implementing the solution. Who will be doing the work
and what, specifically, will they need to do?
b) Project Monitoring and Control Plan: How are you going to ensure that the project is going smoothly? What is your plan of attack to ensure that
all controls are adhered to? What is the defined critical path? Be sure that you frame your response for communicating effectively to your target
audiences.
c) Timeline: What is the estimated amount of time for implementation? Create a visual representation that captures your timeline (e.g., Gantt
chart) based on the systems development life cycle.
Milestones
Milestone One: Business Case Proposal and Introduction
In Module Two, you will submit a business case proposal, which is a summary of your selected business case for the course project. The business case proposal
will be submitted as a Word document and in paragraph form. This business case proposal provides your instructor insight into the project you are selecting and
allows for instructor feedback and guidance in terms of the scope of the business case for the purpose of this course. The first milestone of the course project is
an introduction. This milestone is graded with the Milestone One Rubric.
Milestone Two: Project Plan
In Module Four, you will submit your project plan. The project plan is a Word document that is a combination of a written explanation of the project plan and
the explanation of the control plan. The WBS and timeline are represented with screenshots of the Gantt chart, resource chart, and cost table. Ensure each chart
and graph is properly noted and has text explanation. This milestone is graded with the Milestone Two Rubric.
Milestone Three: System Requirements
In Module Six, you will submit your system requirements. The system requirements model is to be submitted as a Word document that is a combination of
sections: a requirements model, a data process model, a data flow diagram, a data dictionary, an object model, and a use case diagram. Copy the image of your
diagram into your Word document and include text to ensure that the diagram has proper context within the overall system requirements model through written
explanations. Your audience is IT management and the IT project team. This milestone is graded with the Milestone Three Rubric.
Milestone Four: System Design
In Module Eight, you will submit your system design via a Word document. The system design will include visual presentations of each of the following: modeling
for specifications, data design, and user interface design. Each of the diagrams will visually represent your design. The system design additionally will include each
explanation and supporting detail of the system design execution, in a complete and comprehensive write-up. These are the sections Systems Architecture and
Feasibility Analysis. Your audience is IT management and the IT project team. This milestone is graded with the Milestone Four Rubric.
Final Submission: System Proposal Document
In Module Nine, you will submit a systems proposal document. It should be a complete, polished artifact containing all of the critical elements of the final
product. It should reflect the incorporation of feedback gained throughout the course. This milestone will be graded using the Final Project Rubric.
Deliverable Milestones
Milestone
1
Deliverables
Module Due
Grading
Two
Graded separately; Milestone One Rubric
Four
Graded separately; Milestone Two Rubric
Six
Graded separately; Milestone Three Rubric
2
Business Case Proposal and
Introduction
Project Plan
3
System Requirements
4
System Design
Eight
Graded separately; Milestone Four Rubric
Final Product: System Proposal
Document
Nine
Graded separately; Final Project Rubric
Final Project Rubric
Guidelines for Submission: Written components of projects must follow these formatting guidelines when applicable: double spacing, 12-point Times New
Roman font, one-inch margins, and APA citations. The paper should be 30 to 40 pages, not including cover page and resources.
This project uses an integrated rubric in Blackboard. To view the integrated rubric in Blackboard, navigate to the final submission item, click on the title, and then
click the “View Rubric” button. For more information, review these instructions.
Instructor Feedback: This activity uses an integrated rubric in Blackboard. Students can view instructor feedback in the Grade Center. For more information,
review these instructions.
Critical Elements
Background
Exemplary (100%)
Meets “Proficient” criteria and
uses industry-specific
terminology to effectively
communicate and establish
expertise
Problem Statement
Meets “Proficient” criteria and
selects particularly insightful
examples and supporting
evidence that demonstrate a
nuanced understanding of the
problem
Meets “Proficient” criteria and
selects strategies that
demonstrate particular insight
into the needs of the diverse
audiences
Audience
Proficient (90%)
Includes a context that
addresses all essential
paradigms, processes, and
activities of the existing
information technology systems
with sufficient detail for
understanding the systems
proposal
Clearly defines and defends the
problem in need of resolution
by illustrating the impacts to
the enterprise
Needs Improvement (70%)
Includes a context, but it does
not address all essential
paradigms, processes, or
activities of the existing IT
systems or it is not sufficiently
detailed for understanding the
systems proposal
Not Evident (0%)
Does not include a context for
understanding the systems
proposal
Value
6
Defines a problem in need of
resolution, but there are clarity
issues, gaps in the defense, or
inaccuracies in the illustration
Does not include a valid
problem in need of resolution
6
Identifies plausible, distinct
audiences for the proposal
based on the case, and selects
appropriate strategies for
effectively communicating with
each identified audience
Identifies distinct audiences for
the proposal, but lacks
plausibility for the case or does
not select appropriate
strategies for effectively
communicating with each
identified audience
Does not identify distinct
audiences for the proposal
6
Requirements
Modeling
Meets “Proficient” criteria and
selects particularly insightful
examples and supporting
evidence that demonstrate a
nuanced understanding of the
problem
Assesses the current system to
accurately identify the
requirements for the new
system (including the outputs,
inputs, processes, performance,
and controls) using specific
examples
Data Process Model
Meets “Proficient” criteria and
visual representation reflects an
in-depth understanding of the
systems development life cycle
Creates a visual representation
of all relevant data processes,
representing an accurate logical
model of the requirements of
the system based on the
systems development life cycle
Data Flow Diagrams
Meets “Proficient” criteria and
visual representation reflects an
in-depth understanding of the
systems development life cycle
Creates an accurate visual
representation of the data flow
based on the systems
development life cycle
Data Dictionary
Meets “Proficient” criteria and
definitions reflect an in-depth
understanding of the
paradigms, processes, and
activities of IT systems
Meets “Proficient” criteria and
techniques and/or results
demonstrate in-depth
understanding of structure and
object oriented analysis
modeling
Meets “Proficient” criteria and
diagram(s) reflect(s) an in-depth
understanding of the systems
development life cycle
Creates a data dictionary that
annotates the system
requirements and would
effectively build clarity with
relevant audiences
Uses appropriate object
modeling techniques and tools
to effectively describe the
system requirements
Object Modeling
Use Case Diagrams
Creates (a) use case diagram(s)
that accurately outline the
system requirements based on
the systems development life
cycle
Assesses the current system,
but either does not accurately
identify the requirements for
the new system; does not
address the outputs, inputs,
processes, performance, or
controls; or does not use
specific examples
Creates a visual representation
of data processes, but there are
significant gaps or the logical
model of the requirements of
the system is not appropriately
based in the systems
development life cycle
Creates a visual representation
of the data flow, but there are
significant gaps or inaccuracies
based on the systems
development life cycle
Creates a data dictionary that
annotates the system
requirements, but there are
gaps or clarity issues given the
needs of relevant audiences
Uses object modeling
techniques and tools, but either
the tools or the description of
the system requirements are
ineffective
Does not assess the current
system to identify the
requirements for the new
system
6
Does not create a visual
representation of data
processes
6
Does not create a visual
representation of data flow
6
Does not create a data
dictionary that annotates the
system requirements
6
Does not use object modeling
techniques and tools
6
Creates (a) use case diagram(s),
but there are gaps or
inaccuracies in the system
requirements based on the
systems development life cycle
Does not create (a) use case
diagram(s)
6
Specifications
Meets “Proficient” criteria and
physical design reflects an indepth understanding of the
systems development life cycle
Provides a physical design that
comprehensively meets the
specifications outlined in the
systems requirement document
Data Design
Meets “Proficient” criteria and
diagrams reflect in-depth
understanding of structure and
object oriented analysis
modeling
Creates entity relationship
diagrams that accurately
describe the proposed solution,
including 3NF table designs
User Interface Design
Meets “Proficient” criteria and
user interface design reflects an
in-depth understanding of
structure and object oriented
analysis modeling
Illustrates the user interface
design (including HCIs and GUIs)
that follow user-centered
design principles and address all
design requirements
System Architecture
Meets “Proficient” criteria and
system architecture reflects an
in-depth understanding of the
systems development life cycle
Feasibility Analysis
Meets “Proficient” criteria and
evidence and examples reflect
an in-depth understanding of
the paradigms, processes, and
activities of IT systems
Work Breakdown
Structure
Meets “Proficient” criteria and
selects insightful examples that
demonstrate a nuanced
understanding of the
relationship of IT systems
implementation processes
Describes the system
architecture by addressing the
corporate organization and
culture, enterprise resource
planning, total cost of
ownership, scalability,
integration, and interface
requirements, and security in
specific detail
Justifies the proposed solution
by addressing operational,
technical, economic, and
scheduling feasibility in a
manner suitable for the target
audiences
Describes all of the essential
roles and functions required for
implementing the solution with
specific examples
Provides a physical design, but
does not comprehensively meet
the specifications outlined in
the systems requirement
document
Creates entity relationship
diagrams, but there are gaps or
inaccuracies in describing the
solution or does not include
3NF table designs
Does not provide a physical
design
6
Does not create entity
relationship diagrams
5
Illustrates the user interface
design, but does not include
HCIs and GUIs, does not follow
user-centered design principles,
or does not address all design
requirements
Describes the system
architecture, but does not
address the corporate
organization and culture,
enterprise resource planning,
total cost of ownership,
scalability, integration and
interface requirements, or
security in specific detail
Justifies the proposed solution,
but does not fully address
operational, technical,
economic, or scheduling
feasibility in a manner suitable
for their target audiences
Describes the implementation
of the solution, but does not
include all essential roles and
functions or does not include
specific examples
Does not illustrate the user
interface design
5
Does not describe the system
architecture
5
Does not justify the proposed
solution in terms of its
feasibility
5
Does not describe the
implementation of the solution
5
Project Monitoring
and Control Plan
Meets “Proficient” criteria and
plan reflects an in-depth
understanding of the
paradigms, processes, and
activities of IT systems
Timeline
Meets “Proficient” criteria and
visual representation reflects an
in-depth understanding of the
systems development life cycle
Articulation of
Response
Submission is free of errors
related to citations, grammar,
spelling, syntax, and
organization and is presented in
a professional and easy-to-read
format
Includes a project monitoring
and control plan that addresses
all necessary controls and
defines the critical path in a
manner suitable for the target
audiences
Creates a visual representation
of an appropriate timeline for
implementing the solution
based on the systems
development life cycle
Submission has no major errors
related to citations, grammar,
spelling, syntax, or organization
Includes a project monitoring
and control plan, but does not
address all necessary controls
or define the critical path in a
manner suitable for the target
audiences
Creates a visual representation
of the timeline for
implementing the solution, but
it is not fully appropriate based
on the systems development
life cycle
Submission has major errors
related to citations, grammar,
spelling, syntax, or organization
that negatively impact
readability and articulation of
main ideas
Does not include a project
monitoring and control plan
5
Does not create a visual
representation of the timeline
for implementing the solution
5
Submission has critical errors
related to citations, grammar,
spelling, syntax, or organization
that prevent understanding of
ideas
5
Earned Total
100%
Southern New Hampshire University
T 510 Homework Activity Module 4-2
Professor Chakib Chraibi
By: Tyrone Armstrong
Payroll Management System
Introduction:
It is obvious that want to get rid of managing millions of salary details, odd papers,
payroll reports, and pay slips and so on. So we need a payroll processing system that can
generate payroll reports and pay slips within seconds. This can be done by automating the
existing payroll system using a fully customized application that fits to the specific set of
requirements. (Tom, 2012)
Purpose of the Payroll automation:
Main purpose of managing employee payroll system is to create an easy and simple way
not just to automate all of the functionalities that are involved in payroll and managing leaves for
the employees, but also to keep reports of each and every transaction for company management
department with all of the details regarding practice of leave facility.
The purpose of this project is to bring out the best management methods in different
forms of EPM that is in not a product that can be sold, but a tool for managing the inner
operations of Company regarding Payroll and employee leave. (Tom, 2012)
Performance of existing information technology systems:
(a) Present state: Presently salary collection is done manually. Through cross check and
direct cash. All the record is maintained in MS Excel and this cause record Duplication
and mixing etc. Sometimes the client forgot to save the record in excel sheet and the
record is to be entered again.
(b) Problem Statement: composing salary of all employees is a time taking process; also
it takes a lot more time to prepare salary slips in manual systems. As a result a huge
delay in salary distribution is faced by employees. This is a big problem to manage
when salary is not generated in time; the other main problem is error. The chances of
error are more in manual system. To solve all these problem we have to develop a
software which will take good care of these problems.
(c) Audience:
1) Employees
2) Cashier
3) Manager
(d) Systems Requirements:
1. User interfaces:
The software will provide a responsive graphical interface on the front end that is self
explanatory.
2. Hardware interfaces :• Memory of at least 1GB RAM
• With a Hard disk (40 GB)
• A Monitor (interactive system are preferred)
• A Mouse (pointing device)
• A Keyboard (keypad)
• A Printer
3. Software interfaces :
•
Operating System: Windows 7.
•
For Front End : Microsoft VB.Net 2008
•
At Back-end : MS SQL Server 2008
4. Communication interface:
•
Windows Forms
Functional requirements:
▪
Masters:
▪
Employee
▪
Search
▪
Attendance
▪
Salary
▪
Report
Performance requirements:
•
Entire system as a whole should be error free and efficient
•
It must have built in correction and error checking facilities.
•
The system can handle a huge amount of data easily.
Data Process Model:
Data Flow Diagram:Level 1 (High Level Diagram
2nd Level DFD
2nd Level DFD
2nd Level DFD
Data Dictionary
A. Document Release History
B.Circular Details
c. list of amendments done on previous version no.
Table List with Description:
Data Dictionary
1. Table Name: PAY_ALLOWANCE_DEDUCTION
Purpose:
Sl. Field Name Data Type Size Is Required/Not
Key
Description
1
[ALLOW_DEDUC_ID] [int] NOT NULL
P U
Allowance and Deduction id
2
[ALLOW_DEDUC_NAME] [varchar50) NULL
3
[DESCRIPTION] [varchar50) NULL
4
[AllowanceDeductionType] [varchar10) NULL
5
[APPLICABLE] [bit] NULL
U
Allowance and deduction
name
Description of the Allowance
and Deduction
U
Allowance and deduction
type
Allowance or Deduction is
applicable or not
6
[VW_ORDER] [int] NULL
Vworder
7
[CreatedBy] [int] NULL
Data Creation User ID
8
[CreatedDate] [datetime] NULL
Data Creation Date
9
[UpdateBy] [int] NULL
Data Updating User ID
10 [UpdateDate] [datetime] NULL
Data Updating Date
2. Table Name: PAY_Bonus
Purpose:
Sl.
Field Name Data Type Size Is Required/Not
Key
Description
1
[BonusId] [int] NOT NULL
P
ID of the Bonus
2
[BonusName] [varchar50) NOT NULL
U
Name of the Bonus
Allowance and
3
[ALLOW_DEDUC_ID] [int] NOT NULL
U FK
Deduction id
4
[CompanyId] [int] NULL
U FK Company Id
5
[CalculationId] [int] NULL
U FK Calculation Id
6
[CreatedBy] [int] NULL
Data Creation User
ID
7
[CreatedDate] [datetime] NULL
Data Creation Date
8
[UpdateBy] [int] NULL
Data Updating
User ID
9
[UpdateDate] [datetime] NULL
Data Updating
Date
3. Table Name: PAY_BonusEmployeeMapping
Purpose:
Sl. Field Name Data Type Size Is Required/Not Key
P
Description
1
[MappingId] [int] NOT NULL
FK ID of the Mapping
2
[MappingType] [varchar20) NULL
U
Mapping Type
3
[MappingRefId] [varchar30) NULL
U
Mapping Reference ID
4
[BonusId] [int] NULL
U FK Bonus Id
5
[BranchId] [nvarchar4) NULL
U FK Branch Id
6
[CreatedBy] [int] NULL
Data Creation User ID
7
[CreatedDate] [datetime] NULL
Data Creation Date
8
[UpdateBy] [int] NULL
Data Updating User ID
9
[UpdateDate] [datetime] NULL
Data Updating Date
4. Table Name: PAY_DisburseMain
Purpose:
Sl. Field Name Data Type Size Is Required/Not
Key
Description
1
[DisburseId] [bigint] NOT NULL
P U
ID of the Disburse
2
[DisburseDate] [datetime] NULL
3
[VoucherNo] [varchar30) NULL
U
4
[BranchId] [nvarchar4) NULL
U FK ID of the Branch
5
[CreatedBy] [int] NULL
Data Creation User ID
6
[CreatedDate] [datetime] NULL
Data Creation Date
5. Table Name: PAY_DisburseSData Updation User ID
Disburse Date
Voucher No
Purpose:
Sl. Field Name Data Type Size Is Required/Not
Key
Description
1
[DisburseId] [bigint] NOT NULL
U FK ID of the Disburse
2
[EmployeeId] [int] NOT NULL
U FK ID of the employee
3
[PaymentMethod] [varchar50) NOT NULL
Payment Method
4
[Amount] [decimal18 2) NOT NULL
Disburse Amount
5
[ReferenceId] [nvarchar50) NULL
6
U
Reference ID
U
Bank Account Serial
No.
[BankAccountSerialNo] [int] NULL
6. Table Name: PAY_SALARY_SHEET_MAIN
Purpose:
Sl. Field Name Data Type Size Is Required/Not
Key
Description
P U
ID of the Salary
Sheet
1
[SALARY_SHEET_ID] [bigint] NOT NULL
2
[SALARY_YEAR] [int] NOT NULL
U
SALARY YEAR
3
[SALARY_MONTH] [int] NOT NULL
U
Salary Month
4
[VARIFIED_BY] [varchar50) NULL
Verified by User
5
[APPROVED_BY] [varchar50) NULL
Approved by User
6
[VARIFIED_DATE] [datetime] NULL
Verified Date
7
[APPROVED_TIME] [datetime] NULL
Approval Time
8
[BranchId] [nvarchar4) NULL
9
[CreatedBy] [int] NULL
U FK ID of the Branch
Data Creation User
ID
10 [CreatedDate] [datetime] NULL
Data Creation Date
7. Table Name: PAY_SALARY_SHEET_SDATA UPDATION USER ID
Purpose:
Sl. Field Name Data Type Size Is Required/Not
Key
Description
1
P U
ID of the employee
P U
[ALLOW_DEDUC_HEAD] [int] NOT NULL
Head of the
Allowance or
Deduction
3
[AMOUNT] [decimal18 2) NOT NULL
Amount of the pay
salary
4
[BonusId] [int] NULL
2
[IntermediateId] [int] NOT NULL
U FK ID of the Bonus
8. Table Name: PaymentMain
Purpose:
Sl. Field Name Data Type Size Is Required/Not
Key
Description
1
[PaymentId] [nvarchar16) NOT NULL
P
ID of the payment
2
[PaymentDate] [datetime] NOT NULL
3
[BranchId] [char4) NOT NULL
U FK ID of the Branch
4
[SupplierId] [int] NOT NULL
U
Payment Date
ID of the Supplier
[Amount] [decimal18 2) NOT NULL
Amount of the
payment
[CashAmount] [decimal18 2) NOT NULL
Cash Amount of the
payment
7
[ChequeAmount] [decimal18 2) NOT NULL
Cheque Amount of
the payment
8
[CreatedBy] [int] NOT NULL
Data Creation User
5
6
ID
9
[CreatedDate] [datetime] NOT NULL
Data Creation Date
Data Updating User
ID
10 [UpdateBy] [int] NOT NULL
[UpdateDate] [datetime] NOT NULL
Data Updating Date
9. Table Name: PaymentSData Updation User IDSData Updation User ID
Purpose:
Sl. Field Name Data Type Size Is Required/Not
1
[PaymentId] [nvarchar16) NOT NULL
Key
Description
U FK ID of the Payment
2
[PaymentMethodId] [int] NOT NULL
Method of the
Payment
3
[GLCode] [varchar50) NOT NULL
Code of the GL
4
[Amount] [decimal18 2) NOT NULL
Payment Amount
5
[RefNo] [varchar15) NULL
6
[RefDate] [datetime] NULL
7
[BankBranchId] [varchar4) NULL
U
Reference No.
Reference Date
U FK ID of the Bank
Branch
8
[CreatedBy] [int] NOT NULL
Data Creation User
ID
9
[CreatedDate] [datetime] NOT NULL
Data Creation Date
10 [UpdateBy] [int] NOT NULL
Data Updating User
ID
11 [UpdateDate] [datetime] NOT NULL
Data Updating Date
12 [VoucharNo] [varchar50) NULL
U FK Vouchar No.
FEASIBILITY ANALYSIS:
We have analyzed the feasibility of the system in terms of following spans:
1.
2.
3.
4.
Technical Feasibility
Feasibility 3.
Economical Feasibility
4. Scheduled Feasibility
Technical Feasibility: The advance process of payroll the Management structure would be
helpful to the organization since we would create use of one of the presently available reserves of
organization. All tool required for development of are previously available for organization and
the organization does not ensure to acquire new reserves. The technical possibility is also
ascribing to fact that system does not create use of any extra or extra third party components,
which can lead to, increased load on the system.
Operational Feasibility: Payroll Management the System is proposed to give a very accessible
and easy to usage interface. Which is helpful for mutually the operators and visitors who support
in delivering help for system. This system would be without difficulty acceptable between the
visitor and the administrator, as there is no requirement of any distinct skill set for operating
application. This system also advantages the handlers, as they do not require downloading
everything on their terminals rising their proficiency and comfort of use.
Economic Feasibility: Payroll Management the System has a extremely less development the
cost. The less cost is ascribed to use of current resources of organization. As website is extremely
user responsive and simple to use, here is not essential to give extraordinary training to users of
website, therefore saving precious money and time.
Scheduled feasibility: The Projects are continuously provided the deadlines. Each project is
finished in a particular duration. I was the only functioning on this project and I had project
period of three months only. Thus I have attempted best to complete each and every necessity. I
had to finish project on the time and if it were not promising to complete software on the time in
that case I would attempt to satisfy client requirements.
Work Breakdown Structure:-
The Project Monitoring plus the Control Plan:
First 3 weeks we had to do meetings with the client and gather as much requirements as the want
to be in software. Afterward we will arrange about it that in what way to start. After finishing
step 1 just become the calculations that how far it will take to finish and how far resources would
be used up.
In this phase we will monitor our project that how is it going and if there are some issues then we
will try to control them for achieving successful results.
Timeline/ Gantt chart:-
Use Case Diagram:-
Data Design:-
ER diagram:
References:
•
(n.p) “GITL Products – Payroll” retrieved on 23rd May 2015 from:
http://www.godrejinfotech.com/products/payrollb2e.html
•
Tom Jhons Bolipata, 14 November 2012, “AUTOMATED PAYROLL SYSTEM OF TRECE
MARTINES CITY NATIONAL HIGH SCHOOL “retrieved on 23rd May 2015 from:
https://prezi.com/gqrsj7vc0e9g/chapter-iii/
Purchase answer to see full
attachment