Software Development Project Proposal

This assignment details a proposed software development project for a company, focusing on features like card swiping, attendance registration, and future integrations with HR modules. The document highlights the chosen Agile methodology as the most suitable approach given the limited development time and the requirement for continuous updates and improvements throughout the development process. Further aspects like project management tools and references to relevant research are also included.

Time Recording Module
Table of Contents
Log entries........................................................................................................................2
Vision statement................................................................................................................4
WBS..................................................................................................................................4
Gantt chart........................................................................................................................8
Stakeholders......................................................................................................................9
AS IS...............................................................................................................................11
TO BE.............................................................................................................................12
Briefing note....................................................................................................................12
Screen design...................................................................................................................13
Acceptance criteria.........................................................................................................13
Applications architecture................................................................................................14
Executive summary of the RFT (Request for Tender) report.........................................14
Comparison Report.........................................................................................................16
Conclusions.....................................................................................................................17
References.......................................................................................................................18
1

Time Recording Module
Log entries
Options Do nothing - Let the employees use manual sign-in and sign-off processes
for recording their presence in the attendance book
Develop a new Time Recording Module that can be used by workers for
log in and log out through a plastic ID card
Do Nothing Development of TRM
Pros  There would not be any
additional expenses
 Entry through plastic card will
ensure that the entries made are
genuine
 With time recording, company
can have the records
automatically updated without
the need for manual editing
 It would save time of workers
which is currently spent in
manual entries as swiping cards
would be an instant process and
thus, fast
 With automatic recording of
workers data, the data file can
be used for identify patterns
and analysis which can help
company in making decisions
 Card system would ensure that
employees do not miss entering
the attendance as they would
not be able to enter the
premises without that
Cons  Manual entries cause
accidental and deliberate
errors and thus, lacks
 It would be an expense to the
company
 It would need modifications in
2

Time Recording Module
accuracy
 The company is already
receiving complaints and
will continue to receive
them
 Workers tend to record
longer working times
which would lead the
company into giving
more money than the
workers deserve
the working culture and the
organizational processes which
would be a major task
Risks  Errors would risk the
company paying workers
more than what they
worked for
 Errors can cause
conflicts between
workers and the
management
 The Time Recording Module
developed can have unfixed
bugs when launched which can
lead to errors, technical issues
or even complete failure of the
system
 Automation of employee
records can open the company
to the risk of workers data
getting leaked
 Digital system would also
expose systems to cyber
security risks
capital costs No Cost $1200
operating costs No additional cost $25 per month per user
Benefits None  Reduction in errors which
would ensure that the company
is making right amounts in
salaries
 Employees would not lose
money because of mistakes like
forgetting to punch the entry
3

Time Recording Module
into the system
 Administrative burdens would
reduce as attendance would
become automated
 Attendance data would be
accurate with card system
 Entry and exit would be fast
with swiping
 This will give cost saving to
company by reduction of errors,
reduction of time wastage,
increase in accuracy of records,
and ability to analyse workers
data (Ahmad & Laplante, 2009)
Vision statement
This vision of this project is to develop a time recording system that allows workers to mark
their attendance and work duration through the swipe of a card which automatically records
their entry or exit times and allows management to gain the analytical data which would
make it easy for the management to do wage calculations.
WBS
1.0 Management & Support Provisions
1.1 Project Management Processes
1.1.1 Scope Management
1.1.2 HR Management
1.1.3 Procurement management
1.2 Quality control procedure
1.3 Project review
1.4 Budgeting
2.0 Systems Development
2.1 Requirement gathering
2.1.1 Information gathering meeting
2.1.2 Data model
2.1.3 Logical Model
2.2 Designing
4

Time Recording Module
2.2.1 System Architecture
2.2.2 Interface
2.2.3 Information flow
3.0 System Acquisition
3.1 Software procurement
3.1.1 Software specifications development
3.1.2 Vendor Selection
3.1.2.1 Request for proposal
3.1.2.2 Bidding
3.1.2.3 Selection
3.1.3 Order placement
3.1.3.1 Time Recording System Software Specifications
3.1.3.2 Licensing
3.2 Hardware
3.2.1 Hardware specifications
3.2.1.1 Door Access Control System
3.2.1.2 Cards
3.2.2 Hardware procurement
4.0 Integration
4.1 Installation of hardware
4.2 Installation of software
4.2.1 Software customization
4.2.2 Software Installation
4.3 Hardware-Software integration
4.3.1 Card Activation
4.3.2 Software testing
4.3.2.1 Functional testing
4.3.2.2 Unit Testing
5.0 Customer Acceptance
5.1 Customer Acceptance testing
5.2 Customer training
6.0 Data Management
6.1 Data gathering
6.2 Data migration
7.0 Implementation
7.1 Announcement to users
7.2 Go-Live
8.0 Project Closure
8.1 Project closure documentation
8.2 Project Sign-off
(Antón, 2003)
5

Time Recording Module
Gantt chart
6

Time Recording Module
Stakeholders
Stakeholde
r Group
Stakeholder Responsibilities Expectations Interes
t
Influenc
e
7

Time Recording Module
Internal
Stakeholder
s
Project
Sponsor
Review project
business case for
viability and
profitability
Project should
provide strategic
benefit to the
organization and
sponsor must be
providing with the
details of expected
returns.
High High
Project
Execution
Team
Ensure that all
planned activities are
executed within time
and within budget
They should have
clear information
about deliverables
and the quality
requirements for
each software
component
High Moderat
e
Procurement
Manager
Assess and select
best solutions for the
Time Recording
Module
Get the clear
information on
hardware and
software
specifications
Low Low
Top
Management
Review the progress
of project and
provide resources
(Bego, et al., 2006)
Project progress
report upon every
milestone
achievement
Modera
te
High
HR Manager Help in the
information
gathering stage for
understanding
project requirements
Clear
communication on
skills required and
remuneration offered
to each profile under
the project
Modera
te
Low
(Lacaster
Universit
y, 2006)
Workers Understand and use
the card based access
system for
Appropriate
information given on
when the card
High Low
8

Time Recording Module
attendance system would start
and how to use it.
External
Stakeholder
s
Vendors Provide suitable
solution for time
recording module
integration in the
company
Get exact
specifications of the
software and
hardware needed for
the project
Modera
te
High
Consultants Assist company in
identifying and
selecting right
vendors and
solutions
Provide all the
business and
functional needs that
the software product
must fulfil
High Low
Developers Provide coding for
customization of the
time keeping module
for the company
(Farrell, 2007)
Get all the details of
functions that have
to be performed, the
users, access
requirements and
usage requirements
Low Moderat
e (Liu,
2013)
AS IS
The As-Is diagram defines the current processes used in the organization for managing the
attendance of workers. Workers enter the date and time when coming to work in an entry
register. HR administrators check the register every month and finds out about every worker
9

Time Recording Module
if he or she was present on working days. Days when workers are not present are marked as
absent while for other days, total number of hours worked are manually calculated based on
which the wages are calculated for each worker as per the per hour rate (Analysis of various
Software Process Models, 2012).
TO BE
The To-Be diagram defines the future processes that would be used in the organization for
improving the management of the attendance of workers. Workers would use a plastic card to
swipe on the door access system to which creates a timestamp in the system saving the date
and time in a virtual entry register. The data gets stored in the HR Application. HR
administrators use an Admin portal where a dashboard shows monthly attendance of every
worker. The system calculates the total number of hours worked for every person working
automatically. Based on the working hours data, the wages are calculated for each worker as
per the per hour rate by the administrator (Almasri, 2016).
Briefing note
The requirements of the software development may be prioritized based on the needs of the
stakeholders using a method called MoSCoW in which requirements would be categorized
into those that must be developed, those that should be developed, those that can be
developed and those that would or would not be developed. Must requirements are those that
have to be developed to get acceptance from the stakeholders. Should requirements are those
that should be included if the time and budget permits but they are not critical for the project.
10

Time Recording Module
Could are the nice to have requirements that could be developed only when there if the time
and budget fairly permits their development. The ‘Would’ set includes the requirements that
are decided to be developed buy in future (Analysis of various Software Process Models,
2012).
Priorit
y
Requirement
Must Card containing details of workers for swiping and door access system for making
entry through card swiping with timestamp creation every time a card is swiped
Storage of employee details in a backend database and an administrative interface
to see attendance data
Calculation of hourly attendance of workers and dashboard containing summary of
employees attendance
Should Integration with the Human Resource Module
Calculation of wages based on workers attendance
Could Voice based access to selected people from the management in addition to card
swiping
Graphs for comparison of workers attendance for different divisions and projects
Would Analysis of employee data with graphs displayed on dashboard (Liu, 2013)
11

Time Recording Module
Screen design
Acceptance criteria
For developing cards containing details of workers for swiping and door access system for
making entry through card swiping with timestamp creation every time a card is swiped,
following acceptance criteria would be used:
12

Time Recording Module
 Door access system has a small device with monitor and card swiping facility
 Card has all the identity details of employee or worker using it including full name,
contract type, department, project, age, hourly wage, and contract duration (Bruegge
& Johnstone, 1997).
For developing of the storage of employee details in a backend database and an
administrative interface to see attendance data, following acceptance criteria would be used:
 Timestamp of the card swipe created in the database with addition of details of the
employee along with time in the record
 Updating of the administrator dashboard displaying monthly working hours of all
departments and employees
 Download facility for the complete attendance data in excel sheet format (Bego, et al.,
2006)
Applications architecture
13

Time Recording Module
Executive summary of the RFT (Request for Tender) report
The objectives of the request for tender meeting were to provide a brief of the requirement for
the development of time recording module, discussion on the available specifications that
could satisfy these requirements, clarification of the needs for features and quality
requirements, and identification of the scope of the development according to which the
proposals would be prepared for the tender submission (McMunn, 2010).
There were some major questions that were posed by the potential vendors who attended to
meeting and their questions were answered by the management as follows:
 How many types of user profiles are needed and what functionalities they require?
Users include workers as users who would be swiping cards for entry and administrator who
would see the attendance through a dashboard. Administrator should be able to see the total
work hours in a month calculated for every worker.
 What type of access card do you need? (Magnetic stripes, biometric, etc.)
Magnetic stripes that record worker information and the timestamp of the swipe
 How many ID cards do you need in a year?
Between 20 to 100 and each worker may be assigned up to 2 cards (ISBSG, 2012)
 Do you want the software to be computer based?
Yes, we use windows so we need a windows interface
 Do you need any integration with existing systems?
Yes, we need to integrate the module with HR module in future so that attendance
information can be used for wage calculations automatically (Lacaster University, 2006).
 Any other functionality you need now or later?
Voice based access for management users and graphical interpretations of attendance data
needed but not on priority.
 Would you want us to provide you with standard solution or develop a new one for
you?
14

Time Recording Module
We want customized software made for our needs integrated with card systems available
(Giakoumakis & Xylomenos, 1992).
 How long should project take and how flexible are you with dates?
We do not have much time and we need fast development probably within 45 days
The meeting also involved discussions on deliverables, timelines, terms and conditions, and
processes. Highlights of these are presented below:
 The vendor needs to provide development of software, installation of door access
machines, installation of software in company’s server, integration between machines
and server application, and training of administrator on the use of software
(Damsgaard & Karlsbjerg, 2010)
 The entire process of development and installation must be completed within 2
months
 The access control system hardware would be purchased from one vendor while the
software would be procured from other vendor (Devedzic, 2000)
 Company would accept the developed solution only after it is tested and accepted by
users
 The solution must be developed considering ease of use as well as security
considerations
 The design including interface and architecture would be approved by the
management and would not be changed post that except for the addition of new
features if required which would be chargeable
 The vendors would submit technical and commercial bids such that first the technical
bids would be opened and vendors would be selected post that commercial bid would
be opened to see the pricing such that the project would be awarded to the lowest
bidding vendor
 The company would reserve the right to not choose lowest price vendor for any
considerations (Farrell, 2007)
Comparison Report
For the development of the software system for the company, a software development
methodology may be chosen between the simple traditional methodology called Waterfall
15

Time Recording Module
model and the advanced methodology called Agile. Waterfall methodology is most
appropriate when specifications are very clear and can be developed in one sequence with
least need to change. However, the company would be installing the system for the first time
and has no experience of time and attendance functionalities (Cusumano & Smith, 1995). As
of now the company knows some basic application needs but as the project progresses, there
could be major functionalities that management would want to add which could be change in
the dashboard, addition of more information, or more (Awad, 2005). In such cases, waterfall
methodology would turn out to be very costly as the entire development process would have
to be then repeated as a fresh development. However, in case of Agile methodology, making
changes would be easier and faster as it involves iteration. Thus, Agile would ensure that the
project is completed on time while ensuring all functionalities demanded by stakeholders are
incorporated (Chang, 2012).
Conclusions
The report explored the plan for the development of a time recording module for automating
the attendance management system which is currently manual in the company and involves
physical register entries. The manual system is resulting into miscalculations because of
human errors that the company can avoid with the implementation of a digital solution
involving door access control with swipe card entries that would be connected to a virtual
attendance register that would automatically update attendance data based on card swipes by
workers. The report identified some mandatory development requirements such as card
swiping and attendance registered update while other features are expected to be
implemented in near future such as integration with the HR module and calculation of wages
through TRM. As the software would be developed first time for the company and company
has less time for development, the Agile methodology for software development has been
recommended.
16

Time Recording Module
References
Ahmad, N., & Laplante, P. A. (2009). Software Project Management Tools: Making a
Practical Decision Using AHP. Penn State University .
Almasri, A. K. (2016). A PROPOSED HYBRID AGILE FRAMEWORK MODEL FOR
MOBILE APPLICATIONS DEVELOPMENT. International Journal of Software
Engineering & Applications (IJSEA) , 7 (2), 1-9.
Analysis of various Software Process Models. (2012). International Journal of Engineering
Research and Applications (IJERA) , 2 (3), 2015-2021.
Antón, A. I. (2003). Successful Software Projects Need Requirements Planning. North
Carolina State University.
Arora, A., Caulkins, J., & Telang, R. (2003). Provision of Software Quality in the Presence
of Patching Technology. Carnegie Mellon University.
Awad, M. A. (2005). A Comparison between Agile and Traditional Software Development
Methodologies . The University of Western Australia.
Bego, S., Coset, R., Leeuwestein, R., Leijten, M., Linden, I. v., Moreaux, J. M., et al. (2006).
Software Project Management Plan. SPINGRID.
Bruegge, B., & Johnstone, J. (1997). Software Project Management Plan: JAMES Project.
Pittsburgh, PA: Carnegie Mellon University.
Chadli, S. Y., Toval, A., Idri, A., & Nicolás, J. (2016). Software project management tools in
global software development: a systematic mapping study. Research Gate.
Chang, C. (2012). Selecting an Appropriate Software Development Lifecycle (SDL) Model in
an Agency Environment. Retrieved November 12, 2015, from
http://www.metia.com/seattle/chong-chang/2012/08/sdl-model-in-an-agency-environment/
Cusumano, M. A., & Smith, S. (1995). Beyond the Waterfall:Software Development at
Microsoft. International Business Machines.
17

Time Recording Module
Damsgaard, J., & Karlsbjerg, J. (2010). Seven Principles for Selecting Software Packages.
Communications of the ACM.
Devedzic, V. (2000). Software Project Management . Yugoslavia: University of Belgrade.
Farrell, A. (2007). Selecting a Software Development Methodology based on Organizational
Characteristics . ATHABASCA UNIVERSITY .
Giakoumakis, E., & Xylomenos, G. (1992). Evaluation and selection criteria for software
requirements specification standards. CSEWEB.
ISBSG. (2012). Software Development Projects in Government -performance, practices and
predictions. ISBSG.
Lacaster University. (2006). Case Study of Successful Complex IT Projects. THE BRITISH
COMPUTER SOCIETY .
Liu, F. (2013). Rutherford Library Renovation Project Plan. University of Alberta Library.
McMunn, D. (2010). How to interview business people to document a business process.
ComFrame Software.
18