Solved by verified expert:PLEASE REVIEW ATTACHED FILE BEFORE ANSWERINGYou prepared a risk assessment and human resources plan in the previous week. Based on your previous report and after reviewing the project plan, the CIO has identified several concerns. The CIO has asked you to conduct research on project budgeting and estimation tools. You have been asked to incorporate project estimates techniques using PERT, Analogous, and Delphi into the software development plan. Make sure you also could include a discussion on Metrics as part of the project deliverable.Please make sure your overall plan includes the items mentioned above and these items:a company nameidentify a software application/software development projectdetermine which software development method you would use and justify your recommendationprovide an outline of the software development project plan based on the development method you selectedalso include project oversight considerations such as risk management, scheduling, budget, and configuration management
sethholley_swe440_ip3.docx
Unformatted Attachment Preview
Running head: SOFTWARE DEVELOPMENT MODEL
Colorado Technical University
SWE440-1801A-01 Software Project Management
Software Development
Student: Seth Holley
24 Jan 2017
1
SOFTWARE DEVELOPMENT MODEL
2
Contents
Introduction
3
Software Development Model
3
Software Development; Business Requirements and Resources
4
Software Standards
5
Software Standards; IEEE and ISO
5
Institute of Electrical and Electronic Engineering (IEEE)
5
Organization for Standardization (ISO).
6
Incorporation of the ISO and IEEE Standards
7
Risk Assessment
9
Human Resource Plan
11
Identification of the project stakeholders
11
Roles and Responsibilities of the project stakeholders
11
Staff Acquisition
13
Training
13
Recognition and Rewards
13
Work Breakdown Schedule
References
13
15
SOFTWARE DEVELOPMENT MODEL
3
Introduction
Technology has made it easier for today’s organization to enhance their internal and
external operational efficiencies. A financial management system, for example, is a technological
approach and software used by an organization to oversee and control its expense, revenue, and
assets with the aim of ensuring sustainability and maximizing profits. Development of a financial
management system is a process that demands a proper choice of the software lifecycle
methodology and software requirements.
Software Development Model
The most probable traditional software development methodology for the financial
management system is the traditional waterfall model. This methodology is referred to as the
linear-sequential lifecycle model. Ideally, it is very simple to use and understand. When this model
is in use, each phase is expected to be completed before the next phase can begin (Balaji, 2012).
Overlapping the phases is not allowed. The waterfall methodology that will be used in the
development of the software incorporates five phases; Requirement phase, design phase,
development phase, testing phase and deployment phase.
The project is set to take 93 days, which is approximately three (3) months or twelve (12)
weeks. The requirement phase has nine tasks, which are expected to twenty one (21) days or three
(3) weeks. The design phase will have ten tasks, which will take fourteen (14) days or two (2)
weeks. Moreover, the development phase entails ten tasks that will take a period thirty (30) days,
SOFTWARE DEVELOPMENT MODEL
4
which is approximately four (4) weeks. The final phase, deployment, will take a period of seven
(7) days, which is exactly one (1) week.
Software Development; Business Requirements and Resources
The key features and functions of the financial management system to be developed entail;
fixed asset, general ledger, accounts receivable, fast close functions, financial statement and
parallel valuations. The main application functionality that the software is expected to have
include; credit management, biller direct, dispute management and collections management.
Moreover, the functionality should include other functionalities such as cash and liquidity
management, In-house cash, treachery and risk management and bank communication
management.
The main team that will be involved in the development of the financial management
system include;
➢ Project Manager
➢ System Analysts
➢ Software Architect
➢ Software engineers
➢
Development manager
➢ Tester
➢ Network Administrator
SOFTWARE DEVELOPMENT MODEL
5
The software development is a critical process in an organization. Ideally, the professionals
involved in the development process have an obligation of choosing the most appropriate
methodology, project resources, and structure of deployment.
Software Standards
In today’s business environment, software quality has emerged as a critical interest,
precisely to the software managers, developers and the maintainers. With reference to, the fact the
software is evolving is a significant component for a company to compete effectively in the market,
the requirement specification of the software to be easily accessible for the company in
accomplishing its targets is driven by a great level of quality, user convenience and utility
(Medvidovic, 2010). The primary goal of the software standards is to satisfy the customers’
expectations, which is to measure the quality of the software. As such, software standards are the
documented agreements that contain technical specifications and criteria that are consistently used
as guidelines, rules, and definition of characteristics to ensues that the processes, products,
materials, and services fit for their purpose. This text develops a report that analyzes the software
standards and how they can be incorporated into the development of the financial management
system.
Software Standards; IEEE and ISO
The two common providers of the software standards are the Institute of Electrical and
Electronic Engineering (IEEE) and the International Organization for Standardization (ISO).
Institute of Electrical and Electronic Engineering (IEEE)
IEEE identifies itself as a widely recognized large technical professional society that
promotes the development of allied sciences and electro-technology for the advancement of
SOFTWARE DEVELOPMENT MODEL
6
various professions and benefit of humanity (Medvidovic, 2010). This institute fosters the
development of standards that foster become national and international standards. IEEE is trusted
as a guide for engineering, computing and technology information around the world. The main
IEEE standards that can be used in the development of the financial management system include;
➢ IEEE Std. 730-2014 Quality Assurance Processes- This is a revised standard from the
2002 copy that requires for initiation, planning and controlling and execution of the
software quality
➢ IEEE 1008, Software testing- This standard entails a comprehensively defined systematic
and documented unit testing. It utilizes the unit implementation and design, in addition to
the software requirements to determine the completeness of testing (Medvidovic, 2010).
Moreover, the testing process described in the standards comprises of a hierarchy of
activities, phases, and tasks for each activity.
Organization for Standardization (ISO).
The ISO standards create documents that provide guidelines, requirements, and
specifications that can be used consistently to ensure that the products, materials, and processes
are fit for their purposes (Henderson-Sellers, 2014). This organization develops and publishes the
international standards. Some of the ISO standards that can be used in the development if the
financial management system include;
➢ ISO 9126 Software Quality- This ISO standard addresses four main aspects that comprise
of the quality model, internal metrics, external metrics and quality in use metrics.
Moreover, it identifies 6 major quality characteristic of a software; functionality, usability,
efficiency, reliability, maintainability, and portability (Medvidovic, 2010).
SOFTWARE DEVELOPMENT MODEL
7
➢ ISO 12207 Software Lifecycle processes- This standard defines the software engineering
process, tasks and activities associated with the software lifecycle model (Fuggetta, 2014).
In the case of the financial management system, this standard will define the stages and
tasks involved in the waterfall model.
Incorporation of the ISO and IEEE Standards
The incorporation of the ISO and IEEE standards in the development of the financial
system is a critical process that must be approached carefully by the system development team.
The professional team involved should carefully monitor the software standards and practices
(Medvidovic, 2010). Ideally, the plan of incorporation of ISO and IEEE standards will in involve
a series of steps and task.
The first step that will form part of the incorporation is to schedule a kick-off meeting. The
primary purpose of this meeting is to notify all the project members of the intention of using
software standards in the development of the financial management system. As such, the kickoff
meeting intends to get every member on the same page and even open a platform for a joint
decision-making on the use of software standards (Fuggetta, 2014). Preceding the kickoff meeting,
the software team will fully analyze the requirements and specifications of the financial
management system. Such an analysis allows the team to make informed judgments on the
software standards.
Choice of the software standards to be used in the software development is the next step in
the incorporation of ISO and IEEE. Based on the project requirements and specification, the
software team can choose on the most appropriate and applicable software standards. The chosen
IEEE and ISO standards should be able to form part of the successful software development. A
SOFTWARE DEVELOPMENT MODEL
8
well-trained software team will then be chosen to implement the chosen software standards in the
development of the financial management system.
The performance of the software standards in the financial management system can be
monitored through proper coding review. The primary goal of the code review is to systematically
examine the computer source code. As such, the team will be able to identify and misfits and bugs
that had been overlooked during the software development (Medvidovic, 2010). Moreover,
continuous tests should be undertaken to ensure continuous improvement of the software. Testing
also allows a well-proven continuous risk management analysis that monitors the relevance of the
software standards following the ever-evolving rules and guidelines. As such, the team can identify
any standards updates and upgrades.
The advancement of the modern technologically driven society has forced many
organizations to adopt strategic imperatives during the development of a new system. Among the
components used in the software development are the software standards. The two main providers
of software standards are IEEE and ISO foundations. These standards provide documented
agreements with technical specifications that ensure that the developed software meets the
usability, efficiency, reliability, maintainability and portability characteristics.
SOFTWARE DEVELOPMENT MODEL
9
Risk Assessment
As part of managing the function-ability of the financial management system, the control
of risk is an essential approach that any potential problems are identified and efficiently prevented.
During risk assessment, the identification of potential risks should be followed by a suitable plan
or solution (Zavadskas, 2010). Risk assessment in the development of the financial management
system would ensure that the software meets the scope, costs, and quality of the client.
Risk assessment involves a set of procedures that must be carefully established and
completed to ensure maximum protection. The following are five steps of risk assessment that will
be used for the financial management system.
➢ Identification of the hazard- This is the most crucial and essential procedure of the risk
assessment. As such, the process can be achieved by undertaking scrutinized and wellapproached tests (Zavadskas, 2010). The responsible professions will use the Grey-box
testing method, which comprises of white-box and black, box to identify the exact hazard
that is threatening the stability of the financial management system.
➢ Deciding on the negative effects of the Hazard- Upon identification of the hazard, the
responsible team would determine the damages and misfortunes that might occur because
of the problem.
➢ Risk Evaluation and actions- This is the deep assessment and analysis of the harm that is
likely to be caused by the identified hazard. Every involved member in the development of
the financial management system should determine the likelihood of the risks to advance
even after it has been fixed (Zavadskas, 2010). Upon evaluation, the necessary actions
would be taken by ensuring that the most appropriate corrective measures are chosen.
SOFTWARE DEVELOPMENT MODEL
10
➢ Record of the findings- The involved professions will then be expected to document the
findings. The records should comprise of the detailed methods used in the identification of
the procedures, the negative effects and the actions used to address the issue (Zavadskas,
2010). These findings can be presented to every project stakeholder. Moreover, it would
also act as proof of risk assessment of the financial management system.
➢ Review of the risk assessment- This is the final procedure of the of the risk assessment.
The assessment is kept under review to ensure that the selected safety working practices
are continuously applied in the development of the financial management system
(Zavadskas, 2010). The review also ensures that the team takes into account any new
updates of the working practices that might contribute to the safety of the financial
management system.
SOFTWARE DEVELOPMENT MODEL
11
Human Resource Plan
Human Resource Management (HRM) is the systematic and strategic approach of
managing people in ways that would motivate them and maximize their contribution towards the
development of an efficient financial management system (Jiang, 2012).
Identification of the project stakeholders
Inclusive of the identified project team members earlier on, the stakeholders of the financial
management system will entail;
➢ Project Manager
➢ System Analysts
➢ Software Architect
➢ Software engineers
➢ Development manager
➢ Tester
➢ Network Administrator
➢ Client or Customer
Roles and Responsibilities of the project stakeholders
Project Manager
•
Planning and defining the scope of the software development
•
Managing the production of the required deliverables
•
Monitoring the development of the project
•
Ensuring that the project is delivered within the stipulated scope, time and budget
constraints
•
Managing conflict
SOFTWARE DEVELOPMENT MODEL
12
System Analysts
•
Evaluating the software development procedures and processes
•
Develop solutions to any arising problem
•
Validates the results from the testing programs
•
Report any problem that can not be solved by the project manager
Software Architect
•
Design the system from a user perspective
•
Design the usability of the application
•
Design the system application software components
Software developers and engineer
•
Conduct software constructions based on the designs delivered by the software architect
•
Ensure that the system is compatible with the stated business requirements
Development manager
•
Monitor the advances of the software developers and engineer
•
Resolves any arising problems during software development
•
Report conflict or problem that is beyond his capability to the project manager
Tester
•
Perform tests on the software
•
Report to the system analyst
SOFTWARE DEVELOPMENT MODEL
13
Network Administrator
•
Ensure that the system works as expected
•
Report any challenges to the project team
Client or Customer
•
Receives the final project
•
Report any arising challenges
Staff Acquisition
The staff involved in the development of the financial management system will consist
entirely of the internal sources. There will be no outsourcing of the staff. Moreover, all the
resources will remain in the current workplace.
Training
Training has been scheduled to ensure that every team member is fully aware and is
educated on the advances that involve the development of the financial management system.
Moreover, several brochures have been distributed to each project team member to ensure that
they are all aware of their roles and responsibilities.
Recognition and Rewards
The management will recognize the achievement of every individual by providing monetary
awards upon deployment of the financial management system.
Work Breakdown Schedule
The WBS below has been constructed with reference to the software methodology in action.
SOFTWARE DEVELOPMENT MODEL
14
1: Financial Management System
1.4:
Development
1.2:Design
Phase
1.1Requirement
Phase
1.1.1: Kick off
meeting
1.1.2:
Requirement
Classifications
1.1.3: Documenting
the business
requirements
1.1.4:Creating
functional
specifications
1.1.5:Functional and
non-functional
requirement
1.1.6:Project
schedule
1.2.1: Draft of
design specification
1.2.2: Choosing Data model
1.2.3:: Design back-end
and service layout
1.5: Testing
1.6:Deployment
Phase
1.4.1:Building
Database
1.5.1:Functional
testing
1.4.2:Developing
back-end and service
layout
1.5.2:Bug fixes and
data validation
1.4.3:Front-end
and code review
1.5.3:Regression
testing
1.2.4: Update of
project schedule
1.4.5:Code Integration
1.2.5:Approval
of the design
1.5.4:Tests
Approval
1.6.1:Pilot
1.6.2:Production
set-up
1.6.3:Project
Closure
SOFTWARE DEVELOPMENT MODEL
15
References
Balaji, S. &. (2012). Waterfall vs. V-Model vs. Agile: A comparative study on SDLC.
International Journal of Information Technology and Business Management.
Fuggetta, A. &. (2014). Software process. In Proceedings of the on Future of Software
Engineering.
Henderson-Sellers, B. G.-P. (2014). An ontology for ISO software engineering standards: 1)
Creating the infrastructure. Computer Standards & Interfaces.
Jiang, K. L. (2012). How does human resource management influence organizational outcomes?
A meta-analytic investigation of mediating mechanisms. Academy of Management
Journal.
Medvidovic, N. &. (2010). Software architecture: foundations, theory, and practice. In
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering.
Zavadskas, E. K. (2010). Risk assessment of construction projects. Journal of civil engineering
and management.
…
Purchase answer to see full
attachment
