Roles of Management team in System Development
VerifiedAdded on  2023/03/20
|12
|2016
|69
AI Summary
This article discusses the roles of the management team in the development of a system, including financial role, coordination, requirement specification, monitoring, and risk management.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Running head: Smart Enterprise 1
Smart Enterprises
Student Name
Professor’s Name
Institution
Location of Institution
Date
Smart Enterprises
Student Name
Professor’s Name
Institution
Location of Institution
Date
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Smart Enterprises 2
Table of Contents
SECTION ONE...............................................................................................................................3
1.Introduction...................................................................................................................................3
2. Roles of Management team.........................................................................................................3
2.1 Financial role.........................................................................................................................3
2.2 Coordination..........................................................................................................................3
2.3 Requirement specification and determination of project scope.............................................4
2.4 Monitor development process................................................................................................4
2.5 Risk Management..................................................................................................................4
3.0 Expectation................................................................................................................................5
4.0 Methodology..............................................................................................................................5
4.1 Life cycle selection................................................................................................................6
4.1 Requirements analysis...........................................................................................................6
4.2 System design........................................................................................................................6
4.3 System implantation (Coding)...............................................................................................6
4.4 System Testing.......................................................................................................................7
4.5 System Deployment...............................................................................................................7
4.6 Maintenance of the system....................................................................................................7
SECTION TWO..............................................................................................................................8
5 Payroll Processing System............................................................................................................8
5.1 Context Diagram....................................................................................................................8
5.2 Level 0 DFD..........................................................................................................................9
5.3 Flowchart.............................................................................................................................10
6 Conclusion..................................................................................................................................11
References......................................................................................................................................12
Table of Contents
SECTION ONE...............................................................................................................................3
1.Introduction...................................................................................................................................3
2. Roles of Management team.........................................................................................................3
2.1 Financial role.........................................................................................................................3
2.2 Coordination..........................................................................................................................3
2.3 Requirement specification and determination of project scope.............................................4
2.4 Monitor development process................................................................................................4
2.5 Risk Management..................................................................................................................4
3.0 Expectation................................................................................................................................5
4.0 Methodology..............................................................................................................................5
4.1 Life cycle selection................................................................................................................6
4.1 Requirements analysis...........................................................................................................6
4.2 System design........................................................................................................................6
4.3 System implantation (Coding)...............................................................................................6
4.4 System Testing.......................................................................................................................7
4.5 System Deployment...............................................................................................................7
4.6 Maintenance of the system....................................................................................................7
SECTION TWO..............................................................................................................................8
5 Payroll Processing System............................................................................................................8
5.1 Context Diagram....................................................................................................................8
5.2 Level 0 DFD..........................................................................................................................9
5.3 Flowchart.............................................................................................................................10
6 Conclusion..................................................................................................................................11
References......................................................................................................................................12
Smart Enterprises 3
SECTION ONE
1.Introduction
Due to daily changes in technology, there are great changes that need to be done in every
organization to fit in a competitive world. There may be changes in both user and system
requirements that the current system may not be satisfying. The current system may have been
formed when the organization was still young and may not be able to serve the organization well
as it used to, Collier (2015). This will for the management team to plan for an effective and
efficient system.
2. Roles of Management team
2.1 Financial role
The process of developing a system involves different stages. All these stages require money.
Mr. Alex and the management team will have the responsibility of sourcing money to the
development team the enable the work to be done since they will be the stakeholders in this
scenario.
2.2 Coordination
The management team will have to coordinate the group that will be involved in the
development of the accounting information system to make the process a success. Nicholas &
Steyn (2017). System development process does not involve developer alone, there must be
other people like those to gather requirements and the group to test faults in the system.
SECTION ONE
1.Introduction
Due to daily changes in technology, there are great changes that need to be done in every
organization to fit in a competitive world. There may be changes in both user and system
requirements that the current system may not be satisfying. The current system may have been
formed when the organization was still young and may not be able to serve the organization well
as it used to, Collier (2015). This will for the management team to plan for an effective and
efficient system.
2. Roles of Management team
2.1 Financial role
The process of developing a system involves different stages. All these stages require money.
Mr. Alex and the management team will have the responsibility of sourcing money to the
development team the enable the work to be done since they will be the stakeholders in this
scenario.
2.2 Coordination
The management team will have to coordinate the group that will be involved in the
development of the accounting information system to make the process a success. Nicholas &
Steyn (2017). System development process does not involve developer alone, there must be
other people like those to gather requirements and the group to test faults in the system.
Smart Enterprises 4
2.3 Requirement specification and determination of project scope.
Since Mr, Alex will be one of the system users and clients, he will be expected to give some of
the user requirements and functional requirements that the system will be required to meet
before its deployed.
2.4 Monitor development process.
To make sure that the development process is fairing on well, the manager should be on the toes
of the development team. This will enable the project to be completed on time and as required. It
will be most appropriate if the management team employ the following steps in the management.
i) Measuring.
Continuously checking on the progress in the development process to ensure that they are on the
right track.
ii) Evaluation.
Should look at the cause of the problem so that the team should not repeat.
iii) Rectify.
Correct the development team in areas they will have done what was not expected of them. The
correction should be done in the right way.
2.5 Risk Management.
Every entrepreneur is a risk taker, the difference comes in the way of managing risks. The
management team should ensure that any risk that could affect the project is properly managed,
Schaltegger and Burritt (2017).
.
2.3 Requirement specification and determination of project scope.
Since Mr, Alex will be one of the system users and clients, he will be expected to give some of
the user requirements and functional requirements that the system will be required to meet
before its deployed.
2.4 Monitor development process.
To make sure that the development process is fairing on well, the manager should be on the toes
of the development team. This will enable the project to be completed on time and as required. It
will be most appropriate if the management team employ the following steps in the management.
i) Measuring.
Continuously checking on the progress in the development process to ensure that they are on the
right track.
ii) Evaluation.
Should look at the cause of the problem so that the team should not repeat.
iii) Rectify.
Correct the development team in areas they will have done what was not expected of them. The
correction should be done in the right way.
2.5 Risk Management.
Every entrepreneur is a risk taker, the difference comes in the way of managing risks. The
management team should ensure that any risk that could affect the project is properly managed,
Schaltegger and Burritt (2017).
.
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Smart Enterprises 5
3.0 Expectation
Users must be involved in the analysis process of the new Accounting information system.
Among the requirements of any system is the user requirements, there are the expectations of the
users on what the system will do and what the system will not expect to do. The users of the
current system are the one who knows the weakness of the current system that will lead to the
need of a new system hence the need of their involvement, Alvertis et al (2016). When users are
well involved in the development of a new system, it will lead to;
a) Improvement of the final system because the developers will have accurately gotten user
requirements and meeting those requirements won’t be a problem.
b) Will enable system developers to avoid including features that were not expected by the
hence reducing cost.
c) Acceptance testing will not be a problem since acceptance testing is done by the user to
ensure that their requirements are achieved.
d) Reduced cost of training users on how to use the system because the user will have an
earlier understanding of the end system. This will make the system more effective.
e) Easier decision making in the organization since everyone will have a better
understanding of the system.
4.0 Methodology
In adopting new accounting information systems, system development life cycle will be
employed. Vijayasarathy & Butler (2016). This methodology can manage both large and small
systems because of its structure and ability to manage risks. It involves different phases (Stages)
and different people starting from coming up with the idea until when the working system id
deployed.
3.0 Expectation
Users must be involved in the analysis process of the new Accounting information system.
Among the requirements of any system is the user requirements, there are the expectations of the
users on what the system will do and what the system will not expect to do. The users of the
current system are the one who knows the weakness of the current system that will lead to the
need of a new system hence the need of their involvement, Alvertis et al (2016). When users are
well involved in the development of a new system, it will lead to;
a) Improvement of the final system because the developers will have accurately gotten user
requirements and meeting those requirements won’t be a problem.
b) Will enable system developers to avoid including features that were not expected by the
hence reducing cost.
c) Acceptance testing will not be a problem since acceptance testing is done by the user to
ensure that their requirements are achieved.
d) Reduced cost of training users on how to use the system because the user will have an
earlier understanding of the end system. This will make the system more effective.
e) Easier decision making in the organization since everyone will have a better
understanding of the system.
4.0 Methodology
In adopting new accounting information systems, system development life cycle will be
employed. Vijayasarathy & Butler (2016). This methodology can manage both large and small
systems because of its structure and ability to manage risks. It involves different phases (Stages)
and different people starting from coming up with the idea until when the working system id
deployed.
Smart Enterprises 6
4.1 Life cycle selection
Given the fact that the system will involve massive operations, there is a need to have a
consultant who will advise accordingly on what development life cycle to be used. Kerzner &
Kerzner (2017). Having identified the system development life cycle as the core methodology
for its advantages already mentioned, unlike others like agile methodology, Mr. Alex should
consider hiring a consultant, meaning he will incur some additional costs. The ICT staff
members would be of great importance in the identification of the consultant.
4.1 Requirements analysis
Under this stage, all the requirements of the system to be developed, both user requirements and
system requirements, are gathered and requirements document is made for documenting all the
requirements to be used at the end of development of system development to check if all the
earlier specified requirements will have been achieved. Dick, Hull & Jackson (2017). The
people involved at this stage are; the system analyst and the stakeholders.
4.2 System design
After gathering all the requirements, the system development team studies all the specified
requirements and then they come up with the sketch(design) of the proposed system. There is no
coding done at this stage. Examining the requirements will help the development team to come
up with a list of both software and hardware needed in the development process so that they may
be availed. The staff is not involved at this stage.
4.3 System implantation (Coding)
The design made in the earlier stage is now used by the developers to build the system. The
system is not built as a whole at once but the small units called modules are made by different
4.1 Life cycle selection
Given the fact that the system will involve massive operations, there is a need to have a
consultant who will advise accordingly on what development life cycle to be used. Kerzner &
Kerzner (2017). Having identified the system development life cycle as the core methodology
for its advantages already mentioned, unlike others like agile methodology, Mr. Alex should
consider hiring a consultant, meaning he will incur some additional costs. The ICT staff
members would be of great importance in the identification of the consultant.
4.1 Requirements analysis
Under this stage, all the requirements of the system to be developed, both user requirements and
system requirements, are gathered and requirements document is made for documenting all the
requirements to be used at the end of development of system development to check if all the
earlier specified requirements will have been achieved. Dick, Hull & Jackson (2017). The
people involved at this stage are; the system analyst and the stakeholders.
4.2 System design
After gathering all the requirements, the system development team studies all the specified
requirements and then they come up with the sketch(design) of the proposed system. There is no
coding done at this stage. Examining the requirements will help the development team to come
up with a list of both software and hardware needed in the development process so that they may
be availed. The staff is not involved at this stage.
4.3 System implantation (Coding)
The design made in the earlier stage is now used by the developers to build the system. The
system is not built as a whole at once but the small units called modules are made by different
Smart Enterprises 7
developers. The developers divide themselves into different codding groups. The modules are
then brought together to form a system.
4.4 System Testing
All the levels of testing including unit testing which is done by the developer, integration testing
by the developers, system testing by the development team and acceptance testing by the system
users are done at this phase to ensure that the system is properly functioning and all the
requirements have been met, Hooda, & Chhillar (2015).
4.5 System Deployment
Once the acceptance testing has been done by the users and has found that the requirements were
me, the system will be handed out to the organization for use.
4.6 Maintenance of the system
Once the system will have been developed and already in use, improvement will be necessary to
ensure that it continues being effective by producing the desired output.
developers. The developers divide themselves into different codding groups. The modules are
then brought together to form a system.
4.4 System Testing
All the levels of testing including unit testing which is done by the developer, integration testing
by the developers, system testing by the development team and acceptance testing by the system
users are done at this phase to ensure that the system is properly functioning and all the
requirements have been met, Hooda, & Chhillar (2015).
4.5 System Deployment
Once the acceptance testing has been done by the users and has found that the requirements were
me, the system will be handed out to the organization for use.
4.6 Maintenance of the system
Once the system will have been developed and already in use, improvement will be necessary to
ensure that it continues being effective by producing the desired output.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Smart Enterprises 8
SECTION TWO
5 Payroll Processing System
Payroll system calculates the salaries of each employee in an organization by looking at hours
they worked and tax, Valacich, George & Valacich (2017).
5.1 Context Diagram
Figure 1: Payroll System Context Diagram
From the diagram, the biometric system, human resource manager, BDO, the employee and the
vice president are considered the main components. The biometric system captures the employee
time in and time out within a paid month, the human resource keep track of all the employee
information and the respective attendance for the processing of the salary while BDO keeps the
SECTION TWO
5 Payroll Processing System
Payroll system calculates the salaries of each employee in an organization by looking at hours
they worked and tax, Valacich, George & Valacich (2017).
5.1 Context Diagram
Figure 1: Payroll System Context Diagram
From the diagram, the biometric system, human resource manager, BDO, the employee and the
vice president are considered the main components. The biometric system captures the employee
time in and time out within a paid month, the human resource keep track of all the employee
information and the respective attendance for the processing of the salary while BDO keeps the
Smart Enterprises 9
BDO file which is the key requirement for the analysis and finally the vice president, as a
government representative approves the generated reports and updates the bank information.
5.2 Level 0 DFD
Figure 2: Payroll system level 0 DFD
This involves a series of events where the employee produces the payment check, the system
accepts the valid employee transaction details, calculates his or her pay, then generates the
accounting entries which are later used for the general ledger.
BDO file which is the key requirement for the analysis and finally the vice president, as a
government representative approves the generated reports and updates the bank information.
5.2 Level 0 DFD
Figure 2: Payroll system level 0 DFD
This involves a series of events where the employee produces the payment check, the system
accepts the valid employee transaction details, calculates his or her pay, then generates the
accounting entries which are later used for the general ledger.
Smart Enterprises 10
5.3 Flowchart
Figure 3: Payroll Flowchart Diagram
This flow chart explains the processes involved in the overall working of the payroll processing
system. The human resources team marks the start of the whole process. The data is processed to
the final stage of generating reports including the employee paycheck, tax update reports for the
government, statutory reports hence marking the end of the processing process.
5.3 Flowchart
Figure 3: Payroll Flowchart Diagram
This flow chart explains the processes involved in the overall working of the payroll processing
system. The human resources team marks the start of the whole process. The data is processed to
the final stage of generating reports including the employee paycheck, tax update reports for the
government, statutory reports hence marking the end of the processing process.
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Smart Enterprises 11
6 Conclusion
The development of the accounting system and the payroll processing system is designed to
specifically for the achievement of the maximum effectiveness and efficiency. This will greatly
reduce the time consumed in the handling of the payment process. With this development, the
system will ensure proper reports are generated hence reducing the bulk of data entry and time
considerably for the organization implementing the system.
6 Conclusion
The development of the accounting system and the payroll processing system is designed to
specifically for the achievement of the maximum effectiveness and efficiency. This will greatly
reduce the time consumed in the handling of the payment process. With this development, the
system will ensure proper reports are generated hence reducing the bulk of data entry and time
considerably for the organization implementing the system.
Smart Enterprises 12
References
Alvertis, I., Koussouris, S., Papaspyros, D., Arvanitakis, E., Mouzakitis, S., Franken, S., ... &
Prinz, W. (2016). User involvement in software development processes. Procedia
Computer Science, 97, 73-83.
Collier, P. M. (2015). Accounting for managers: Interpreting accounting information for decision
making. John Wiley & Sons.
Dick, J., Hull, E., & Jackson, K. (2017). Requirements engineering. Springer.
Hooda, I., & Chhillar, R. S. (2015). Software test process, testing types, and techniques.
International Journal of Computer Applications, 111(13).
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business, and
technology. Routledge.
Schaltegger, S., & Burritt, R. (2017). Contemporary environmental accounting: issues, concepts,
and practice. Routledge.
Valacich, J. S., George, J. F., & Valacich, J. S. (2017). Modern systems analysis and design.
Pearson Education Limited.
Vijayasarathy, L. R., & Butler, C. W. (2016). Choice of software development methodologies:
Do organizational, project, and team characteristics matter? IEEE Software, 33(5), 86-94.
References
Alvertis, I., Koussouris, S., Papaspyros, D., Arvanitakis, E., Mouzakitis, S., Franken, S., ... &
Prinz, W. (2016). User involvement in software development processes. Procedia
Computer Science, 97, 73-83.
Collier, P. M. (2015). Accounting for managers: Interpreting accounting information for decision
making. John Wiley & Sons.
Dick, J., Hull, E., & Jackson, K. (2017). Requirements engineering. Springer.
Hooda, I., & Chhillar, R. S. (2015). Software test process, testing types, and techniques.
International Journal of Computer Applications, 111(13).
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business, and
technology. Routledge.
Schaltegger, S., & Burritt, R. (2017). Contemporary environmental accounting: issues, concepts,
and practice. Routledge.
Valacich, J. S., George, J. F., & Valacich, J. S. (2017). Modern systems analysis and design.
Pearson Education Limited.
Vijayasarathy, L. R., & Butler, C. W. (2016). Choice of software development methodologies:
Do organizational, project, and team characteristics matter? IEEE Software, 33(5), 86-94.
1 out of 12
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
 +13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024  |  Zucol Services PVT LTD  |  All rights reserved.