Analyzing Software Design Activities with Engineering Discipline
VerifiedAdded on 2023/06/03
|27
|9626
|57
Report
AI Summary
This report examines software design activities from an engineering design perspective, focusing on incorporating engineering discipline to enhance software quality and meet customer needs. It evaluates the efficiency of engineering practices in improving software design, emphasizing requirement identification, effective design development, and system management. The report highlights the importance of user participation and the role of functional and non-functional specifications. It explores design planning, problem space decision, and solution space design processes. The literature review concludes that deploying engineering principles improves software design activities, particularly in developing component-level architecture to meet user specifications from the project initiation phase. The study uses qualitative research methodology for analyzing the software design activities incorporated with the engineering design practices.

Examining software design activities with the lenses from engineering design discipline
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Executive summary:
The purpose of this paper is to determine software designing process and identifying the
challenges which comes in the development of the software program. The focus should be
given on incorporating the engineering discipline for enhancing the quality of the software
design to meet the requirement and need of the customers. The scope of the project is to
determine and evaluate the efficiency of the engineering discipline and working model to
improve the design of the software to meet the desired expectation of the users. The
engineering discipline helps in identifying the requirement for the software design,
developing effective and efficient design of the proposed software, and managing and
upgrading the system requirement according to the need and requirement of the user. The
active participation of the users helps in determining the efficiency of the project for
operation. The success and failure of the project can be determined in the implementation
phase only. The functional and non-functional specification of the software should be
according to the requirement specified by the user in the proposal plan. The expansion of the
designing activities should be done for resolving the complexities of the undertaken software
development process. It is majorly depends on four process which are categorized as Design
planning process, problem space decision process, and solution space design process. The
efficiency of the software can be improved by developing an effective program for
undergoing the component level design to accomplish the given task effectively within the
scheduled time and cost to omit complicacies with the end result of the project. The study of
the literature review helps in concluding that the efficiency of the software designing
activities can be improved by deploying the engineering practices principles. The central
focus should be given on developing the component level architecture design model so that
the final result is capable of meeting the requirement specification plan developed by the user
during the project initiation phase.
The purpose of this paper is to determine software designing process and identifying the
challenges which comes in the development of the software program. The focus should be
given on incorporating the engineering discipline for enhancing the quality of the software
design to meet the requirement and need of the customers. The scope of the project is to
determine and evaluate the efficiency of the engineering discipline and working model to
improve the design of the software to meet the desired expectation of the users. The
engineering discipline helps in identifying the requirement for the software design,
developing effective and efficient design of the proposed software, and managing and
upgrading the system requirement according to the need and requirement of the user. The
active participation of the users helps in determining the efficiency of the project for
operation. The success and failure of the project can be determined in the implementation
phase only. The functional and non-functional specification of the software should be
according to the requirement specified by the user in the proposal plan. The expansion of the
designing activities should be done for resolving the complexities of the undertaken software
development process. It is majorly depends on four process which are categorized as Design
planning process, problem space decision process, and solution space design process. The
efficiency of the software can be improved by developing an effective program for
undergoing the component level design to accomplish the given task effectively within the
scheduled time and cost to omit complicacies with the end result of the project. The study of
the literature review helps in concluding that the efficiency of the software designing
activities can be improved by deploying the engineering practices principles. The central
focus should be given on developing the component level architecture design model so that
the final result is capable of meeting the requirement specification plan developed by the user
during the project initiation phase.

Contents
Executive summary:...................................................................................................................1
Introduction................................................................................................................................3
Research Aim.............................................................................................................................4
Research Objectives...................................................................................................................4
Research Scope..........................................................................................................................5
Research Questions....................................................................................................................5
Research Methodology...............................................................................................................5
Literature Review.......................................................................................................................5
Findings....................................................................................................................................16
Discussion................................................................................................................................20
Conclusion................................................................................................................................22
References:...............................................................................................................................24
Executive summary:...................................................................................................................1
Introduction................................................................................................................................3
Research Aim.............................................................................................................................4
Research Objectives...................................................................................................................4
Research Scope..........................................................................................................................5
Research Questions....................................................................................................................5
Research Methodology...............................................................................................................5
Literature Review.......................................................................................................................5
Findings....................................................................................................................................16
Discussion................................................................................................................................20
Conclusion................................................................................................................................22
References:...............................................................................................................................24
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

Examining software design activities with the lenses from engineering design discipline
Introduction
The quality of the software depends upon the clear and concise analysis of the requirement
and the features desired by the customers. The requirement specification should be
demonstrated for improving the functionality of the software. The engineering design
practices play a vital role in the formulation of the software design components to increase
the level of satisfaction of the customers. The sustainability of the project depends upon the
initialization of the problem solving structural demand for managing the risks and
uncertainties with the software development process. The efficiency and quality of the
software depends upon the decision making capability to resolve vulnerabilities associated
with the development process. The systematic approaches should be laid down for analysing
the demand and uncertainties complies with the implementation approach. The emphasis
should be given on the engineering practices because it helps in defining the requirement and
the end services required from the developed software. The requirement engineering
procedures are used for defining the expectation of the users to get the high quality functional
program of the software model. The errors and complexities of the program can be resolved
by managing the tactics of engineering discipline for balancing the need and requirement of
the software. The critical analysis of the software process helps in defining the specification
of errors and validation control for evaluating the complexities. The dependency of the
software design depends on the four main process which are named as feasibility analysis and
evaluation, requirement elicitation process, determining the clear requirement specification,
and validation and verification of the requirement. The feasibility analysis helps in
identifying the gaps and flaws in the exisiting software technology. The elicitation phase
focuses on collecting the data from different sources to analyse the requirement and demand
of the user. The specification and requirement plan should be developed for analysing the
need and expectation. The meetings arranged with the customers helps in identifying the
validation and verification of the process. The purpose of this paper is to determine software
designing process and identifying the challenges which comes in the development of the
software program. The focus should be given on incorporating the engineering discipline for
enhancing the quality of the software design to meet the requirement and need of the
customers. The decision making efficiency can be improved by implementing the engineering
practise in the working model of the software design process because it helps in evaluating
Introduction
The quality of the software depends upon the clear and concise analysis of the requirement
and the features desired by the customers. The requirement specification should be
demonstrated for improving the functionality of the software. The engineering design
practices play a vital role in the formulation of the software design components to increase
the level of satisfaction of the customers. The sustainability of the project depends upon the
initialization of the problem solving structural demand for managing the risks and
uncertainties with the software development process. The efficiency and quality of the
software depends upon the decision making capability to resolve vulnerabilities associated
with the development process. The systematic approaches should be laid down for analysing
the demand and uncertainties complies with the implementation approach. The emphasis
should be given on the engineering practices because it helps in defining the requirement and
the end services required from the developed software. The requirement engineering
procedures are used for defining the expectation of the users to get the high quality functional
program of the software model. The errors and complexities of the program can be resolved
by managing the tactics of engineering discipline for balancing the need and requirement of
the software. The critical analysis of the software process helps in defining the specification
of errors and validation control for evaluating the complexities. The dependency of the
software design depends on the four main process which are named as feasibility analysis and
evaluation, requirement elicitation process, determining the clear requirement specification,
and validation and verification of the requirement. The feasibility analysis helps in
identifying the gaps and flaws in the exisiting software technology. The elicitation phase
focuses on collecting the data from different sources to analyse the requirement and demand
of the user. The specification and requirement plan should be developed for analysing the
need and expectation. The meetings arranged with the customers helps in identifying the
validation and verification of the process. The purpose of this paper is to determine software
designing process and identifying the challenges which comes in the development of the
software program. The focus should be given on incorporating the engineering discipline for
enhancing the quality of the software design to meet the requirement and need of the
customers. The decision making efficiency can be improved by implementing the engineering
practise in the working model of the software design process because it helps in evaluating
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

the gaps and areas of improvement in the clear and systematic manner. The efficiency of the
software depends upon the data gathered from different online and offline sources to prepare
the requirement specification plan and implication of verification and validation process to
complete the design in the direction of the customer expectation to reach their level of
satisfaction. In this paper, we are going to study the literature review for examining the
activities incorporated in the development process of the software design and combining it
with engineering discipline to get the better improved quality product at the end of the
software development process.
Research Aim
The aim of the research is to deploy the empirical literature review on combining the
efficiency of the engineering discipline for the development of the software design. The
purpose of this paper is to analyse the software design activities with the implication of
engineering discipline.
Research Objectives
The objectives of this research are:
Empirical study of literature review for analysing the facts and figures related to the
software development process
Analysing the efficiency and decision impact on the designing activities
Analysing the role of software verification and validation procedures for achieving
the expectation of the customers
Analysing the efficiency of the engineering practices in the development of the
software design
Analysing the impact of requirement specification plan on the working procedures of
software development program
Analysing the challenges which comes in the field of software designing
Analysing the implication of engineering practices to meet the expectation of the
users
Analysing the relationship between the software development and designing process
and the engineering practices.
software depends upon the data gathered from different online and offline sources to prepare
the requirement specification plan and implication of verification and validation process to
complete the design in the direction of the customer expectation to reach their level of
satisfaction. In this paper, we are going to study the literature review for examining the
activities incorporated in the development process of the software design and combining it
with engineering discipline to get the better improved quality product at the end of the
software development process.
Research Aim
The aim of the research is to deploy the empirical literature review on combining the
efficiency of the engineering discipline for the development of the software design. The
purpose of this paper is to analyse the software design activities with the implication of
engineering discipline.
Research Objectives
The objectives of this research are:
Empirical study of literature review for analysing the facts and figures related to the
software development process
Analysing the efficiency and decision impact on the designing activities
Analysing the role of software verification and validation procedures for achieving
the expectation of the customers
Analysing the efficiency of the engineering practices in the development of the
software design
Analysing the impact of requirement specification plan on the working procedures of
software development program
Analysing the challenges which comes in the field of software designing
Analysing the implication of engineering practices to meet the expectation of the
users
Analysing the relationship between the software development and designing process
and the engineering practices.

Research Scope
The scope of the project is to determine and evaluate the efficiency of the engineering
discipline and working model to improve the design of the software to meet the desired
expectation of the users. The feasibility analysis helps in identifying the gaps and flaws in the
existing software technology. The elicitation phase focuses on collecting the data from
different sources to analyse the requirement and demand of the user. The development of the
requirement specification plan with the implication of the engineering discipline helps in
systematic organization of the software program. The focus should be given on the challenge
which comes forward in the achieving the quality product at the end of the complete cycle.
The areas of improvement should be systematically reviewed so that corrective action plan
can be implied on the development process.
Research Questions
Research Methodology
The qualitative research methodology is deployed for analysing the software design activities
incorporated with the engineering design practices. The major emphasis should be given on
the selection procedure for the literature from online and offline sources to get relevant data
for the research study. The study of the literature review helps in collecting appropriate facts
and information to analyse the challenges and relationship in the development of the software
design and implication of the engineering practices. The systematic study and data matrix
should be developed for managing the requirement in the software design. The research study
helps in analysing the verification and validation process to meet the requirement of the
users. The study of the literary sources helps in analysing the view point of different
researchers in the development of the software design specification and gets the quality
product at the end of the project completion. The literature study helps in identifying that the
decision making efficiency can be improved by implementing the engineering practise in the
working model of the software design process because it helps in evaluating the gaps and
areas of improvement in the clear and systematic manner.
Literature Review
The literature review helps in analysing and evaluating the working procedure laid down for
the systematic organization of the software development process. The major factors which
The scope of the project is to determine and evaluate the efficiency of the engineering
discipline and working model to improve the design of the software to meet the desired
expectation of the users. The feasibility analysis helps in identifying the gaps and flaws in the
existing software technology. The elicitation phase focuses on collecting the data from
different sources to analyse the requirement and demand of the user. The development of the
requirement specification plan with the implication of the engineering discipline helps in
systematic organization of the software program. The focus should be given on the challenge
which comes forward in the achieving the quality product at the end of the complete cycle.
The areas of improvement should be systematically reviewed so that corrective action plan
can be implied on the development process.
Research Questions
Research Methodology
The qualitative research methodology is deployed for analysing the software design activities
incorporated with the engineering design practices. The major emphasis should be given on
the selection procedure for the literature from online and offline sources to get relevant data
for the research study. The study of the literature review helps in collecting appropriate facts
and information to analyse the challenges and relationship in the development of the software
design and implication of the engineering practices. The systematic study and data matrix
should be developed for managing the requirement in the software design. The research study
helps in analysing the verification and validation process to meet the requirement of the
users. The study of the literary sources helps in analysing the view point of different
researchers in the development of the software design specification and gets the quality
product at the end of the project completion. The literature study helps in identifying that the
decision making efficiency can be improved by implementing the engineering practise in the
working model of the software design process because it helps in evaluating the gaps and
areas of improvement in the clear and systematic manner.
Literature Review
The literature review helps in analysing and evaluating the working procedure laid down for
the systematic organization of the software development process. The major factors which
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

are responsible for designing the software design specification are goal, requirement matrix,
and innovative ideas and features required in the software functional program. The authors
presented their view on software development process which are comprised of series of
sequential step which should be follow for collecting data from different sources, deploying
feasibility analysis for identifying the gaps and flaws, estimating the requirement
specification plan, designing of the software model, testing and evaluating the results of the
software, matching the software outcome and expectation of the customers, implementing the
software for operational purpose, and reviewing the project success for improvement [1]. The
required changes can be identified in the testing phase to meet the desired level of
expectation of the customers [1]. The overall functionality of the design depends upon
organization of the engineering practices.
The engineering discipline helps in identifying the requirement for the software design,
developing effective and efficient design of the proposed software, and managing and
upgrading the system requirement according to the need and requirement of the user [2]. The
focus should be given on engineering practices for enhancing the decision making
capabilities of the project manager to get and organize the effective software design
specification. The software design paradigm should be prepared for identifying and
comparing the developed outcome with the expected outcome. The elaboration of the
software design can takes place by taking effective decision in the systematic synchronisation
of the different phases of the software development plan [3]. The authors give attention on
the decision making process to resolve the vulnerabilities and complexities associated with
the working model of the software plan. The effective management of the resources and
incorporation of the communication tools helps in meeting the requirement of the designing
features in the software. The gaps in the software plan can be evaluated for highlighting the
problems to take effective decision. There are different methodologies which are used for
designing the software such as agile, waterfall, V-model, and others [4]. The quality of the
software can be received by the taking active participation of the users to verify and validate
the development functional module of the software.
The unclear requirement specification plan results in the poor quality of the outcome and
software fails in meeting the requirement of the users. The authors in their research work
focuses on identifying the role played by the engineering practices in the software
development and designing life cycle [5]. The controlling and monitoring of the software
and innovative ideas and features required in the software functional program. The authors
presented their view on software development process which are comprised of series of
sequential step which should be follow for collecting data from different sources, deploying
feasibility analysis for identifying the gaps and flaws, estimating the requirement
specification plan, designing of the software model, testing and evaluating the results of the
software, matching the software outcome and expectation of the customers, implementing the
software for operational purpose, and reviewing the project success for improvement [1]. The
required changes can be identified in the testing phase to meet the desired level of
expectation of the customers [1]. The overall functionality of the design depends upon
organization of the engineering practices.
The engineering discipline helps in identifying the requirement for the software design,
developing effective and efficient design of the proposed software, and managing and
upgrading the system requirement according to the need and requirement of the user [2]. The
focus should be given on engineering practices for enhancing the decision making
capabilities of the project manager to get and organize the effective software design
specification. The software design paradigm should be prepared for identifying and
comparing the developed outcome with the expected outcome. The elaboration of the
software design can takes place by taking effective decision in the systematic synchronisation
of the different phases of the software development plan [3]. The authors give attention on
the decision making process to resolve the vulnerabilities and complexities associated with
the working model of the software plan. The effective management of the resources and
incorporation of the communication tools helps in meeting the requirement of the designing
features in the software. The gaps in the software plan can be evaluated for highlighting the
problems to take effective decision. There are different methodologies which are used for
designing the software such as agile, waterfall, V-model, and others [4]. The quality of the
software can be received by the taking active participation of the users to verify and validate
the development functional module of the software.
The unclear requirement specification plan results in the poor quality of the outcome and
software fails in meeting the requirement of the users. The authors in their research work
focuses on identifying the role played by the engineering practices in the software
development and designing life cycle [5]. The controlling and monitoring of the software
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

design activities can be effectively done by implementing the framework of engineering
practices which are comprised of five phases which are precisely described below:
Defining the clear statement of requirement:
The active participation of the user and software designer helps in developing the clear,
precise, and concise requirement specification statement. The focus should be given on the
sources used for collecting the data for identifying the problems in the currently existing
software. The problems are identified to get the clear idea about the features in the newly
designed software model. The defining the clear statement helps in giving proper direction to
the research study for collecting the required data and information [5]. The engineering
practices helps in arranging the requirement in the systematic format so that the designer can
easily able to deduct the requirement and carried out their designing activities. The
backtracking process should be laid down for identifying the change in the requirement of the
users so that there should be no difference in the actual output of the development process.
The requirement of the user should be clearly defined by analysing the inconsistency in the
previous solution. The problem statement should be prepared for formulating the
unambiguous structure of the requirement plan. The data should be collected for formulating
the software plan according to the requirement raised by the customers [6].
Requirement gathering:
The data and information should be collected from different sources to enlighten the
functional efficiency of the software model. The elicitation phase focuses on collecting the
data from different sources to analyse the requirement and demand of the user. The
specification and requirement plan should be developed for analysing the need and
expectation. The meetings arranged with the customers helps in identifying the validation and
verification of the process [7]. The study of the similar software product should be taken
under consideration because it helps in analysing the need and expectation of the customers.
The review and feedback should be collected on the older software design so that the research
can be done to meet the specification posted by the user. The division of role and
responsibilities of the team members should be done according to the requirement plan of the
project. The parameters which should be checked for requirement gathering program are
identifying the structure of the problem, analysing the proposed solution for optimizing the
software process, analysing the improvement in the existing system, identifying the right
practices which are comprised of five phases which are precisely described below:
Defining the clear statement of requirement:
The active participation of the user and software designer helps in developing the clear,
precise, and concise requirement specification statement. The focus should be given on the
sources used for collecting the data for identifying the problems in the currently existing
software. The problems are identified to get the clear idea about the features in the newly
designed software model. The defining the clear statement helps in giving proper direction to
the research study for collecting the required data and information [5]. The engineering
practices helps in arranging the requirement in the systematic format so that the designer can
easily able to deduct the requirement and carried out their designing activities. The
backtracking process should be laid down for identifying the change in the requirement of the
users so that there should be no difference in the actual output of the development process.
The requirement of the user should be clearly defined by analysing the inconsistency in the
previous solution. The problem statement should be prepared for formulating the
unambiguous structure of the requirement plan. The data should be collected for formulating
the software plan according to the requirement raised by the customers [6].
Requirement gathering:
The data and information should be collected from different sources to enlighten the
functional efficiency of the software model. The elicitation phase focuses on collecting the
data from different sources to analyse the requirement and demand of the user. The
specification and requirement plan should be developed for analysing the need and
expectation. The meetings arranged with the customers helps in identifying the validation and
verification of the process [7]. The study of the similar software product should be taken
under consideration because it helps in analysing the need and expectation of the customers.
The review and feedback should be collected on the older software design so that the research
can be done to meet the specification posted by the user. The division of role and
responsibilities of the team members should be done according to the requirement plan of the
project. The parameters which should be checked for requirement gathering program are
identifying the structure of the problem, analysing the proposed solution for optimizing the
software process, analysing the improvement in the existing system, identifying the right

decision for solving the problems, identifying the economic and financial stability of the
software solution, and consideration should be given on problem specification [8].
Identifying alternative solutions:
The focus should be given on designing and formulating different innovative ideas to develop
the software according to the requirement of the users. The alternative solution provides
different path to initialize the functions and features in the required software model. The
functional specification should be designed by incorporating the ideas and innovation of the
different researchers. The dependency of the software process should be determined for
analysing the effectiveness of the different alternative solution [9]. The survey should be
conducted for evaluating the performance of different alternatives so that the right
development model can be prepared which is capable of meeting all the requirement of the
customers. The alternatives solution should be prepared for resolving the issues and
complexities associated with the project. The potential outcome of the project should be
measured for taking innovative solution to resolve the complexities. The success criteria of
the solution should be identified so that performance of the software can be relatively
measured. The engineering practices should be applied on the design process for analysing
the priority associated with the software process [10].
Analysing and selecting the best alternative solution:
The procedures should be laid down for measuring the efficiency and performance of the
different alternatives in the second phase of engineering practices. The outcome of the
different alternatives should be measured for selecting the best solution for developing the
required design of the software. The focus should be given on incorporating the engineering
discipline for enhancing the quality of the software design to meet the requirement and need
of the customers. The decision making efficiency can be improved by implementing the
engineering practise in the working model of the software design process because it helps in
evaluating the gaps and areas of improvement in the clear and systematic manner [11]. The
performance of the software solution should be measured on the following factors which are
categorised as designing the software component at low cost, designing the innovative
methodology, analysing the impact of the software on the operational efficiency of the users,
determining the factors responsible for the successful accomplishment of the project,
identifying the area of improvement, evaluating the difference between the actual output and
required output of the software process. The efficiency of the software can be tested on the
software solution, and consideration should be given on problem specification [8].
Identifying alternative solutions:
The focus should be given on designing and formulating different innovative ideas to develop
the software according to the requirement of the users. The alternative solution provides
different path to initialize the functions and features in the required software model. The
functional specification should be designed by incorporating the ideas and innovation of the
different researchers. The dependency of the software process should be determined for
analysing the effectiveness of the different alternative solution [9]. The survey should be
conducted for evaluating the performance of different alternatives so that the right
development model can be prepared which is capable of meeting all the requirement of the
customers. The alternatives solution should be prepared for resolving the issues and
complexities associated with the project. The potential outcome of the project should be
measured for taking innovative solution to resolve the complexities. The success criteria of
the solution should be identified so that performance of the software can be relatively
measured. The engineering practices should be applied on the design process for analysing
the priority associated with the software process [10].
Analysing and selecting the best alternative solution:
The procedures should be laid down for measuring the efficiency and performance of the
different alternatives in the second phase of engineering practices. The outcome of the
different alternatives should be measured for selecting the best solution for developing the
required design of the software. The focus should be given on incorporating the engineering
discipline for enhancing the quality of the software design to meet the requirement and need
of the customers. The decision making efficiency can be improved by implementing the
engineering practise in the working model of the software design process because it helps in
evaluating the gaps and areas of improvement in the clear and systematic manner [11]. The
performance of the software solution should be measured on the following factors which are
categorised as designing the software component at low cost, designing the innovative
methodology, analysing the impact of the software on the operational efficiency of the users,
determining the factors responsible for the successful accomplishment of the project,
identifying the area of improvement, evaluating the difference between the actual output and
required output of the software process. The efficiency of the software can be tested on the
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

operational functionality and the involvement of the human resources in the completion of
the project plan [12].
Testing of the software design:
The test plan should be prepared for conducting the dry run of the developed software so as
to evaluate that it meets the customer requirement or not. The efficiency of the software
capabilities and functional module can be tested. The parameters which are used for
analysing the functional structure of the software are demand of the user, software design
activities, and performance and output of the developed product [13]. The result of the testing
procedures helps in analysing the areas of improvement for the progress of the software
model. The required features are updated according to the changes required by the customers.
The software is ready for the implementation process after including the procedures of
updating the area of improvement.
Implementation of the software:
The software is ready for the process of installation and implementation so that it can be
provided to the users for operation. The active participation of the users helps in determining
the efficiency of the project for operation. The success and failure of the project can be
determined in the implementation phase only. The functional and non-functional
specification of the software should be according to the requirement specified by the user in
the proposal plan [13]. The accomplishment of the goals and objectives helps in developing
and manufacturing similar product for the sale of the software in the global market.
The following diagram shows the systematic model of the engineering Design process:
the project plan [12].
Testing of the software design:
The test plan should be prepared for conducting the dry run of the developed software so as
to evaluate that it meets the customer requirement or not. The efficiency of the software
capabilities and functional module can be tested. The parameters which are used for
analysing the functional structure of the software are demand of the user, software design
activities, and performance and output of the developed product [13]. The result of the testing
procedures helps in analysing the areas of improvement for the progress of the software
model. The required features are updated according to the changes required by the customers.
The software is ready for the implementation process after including the procedures of
updating the area of improvement.
Implementation of the software:
The software is ready for the process of installation and implementation so that it can be
provided to the users for operation. The active participation of the users helps in determining
the efficiency of the project for operation. The success and failure of the project can be
determined in the implementation phase only. The functional and non-functional
specification of the software should be according to the requirement specified by the user in
the proposal plan [13]. The accomplishment of the goals and objectives helps in developing
and manufacturing similar product for the sale of the software in the global market.
The following diagram shows the systematic model of the engineering Design process:
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

The designing of the software depends upon the set of activities which helps in analysing the
formulation of the given task for increasing the efficiency of the desired outcome for getting
the desired result [14]. The list of software activities which are undertaken for meeting the
requirement of the user are highlighted below:
Analysis of the functional module: The focus should be given on identifying the functional
efficiency of the undertaken project and the requirement plan. The consideration should be
given on the success parameters used for the critical analysing of the undertaken project. The
requirement of the new design and features of the software should be determined so that the
efficiency and the human intervention can be effectively reduced. The durability and cost
associated with the development of software should be determined [15].
Ergonomic phase: The involvement of the human engineering design should be evaluated for
getting the best effective software design. The people should be involved in controlling the
procedure of analysing the required output of the undertaken process. The factors responsible
for the software design should comply the requirement of the user to get desired outcome.
There are challenges in identifying the need and requirement of the stakeholder clearly so that
concise problem statement can be prepared. The active participation of the user should help
in diagnosing the successful module of the software quality standards. The communication
tools should be implemented for getting the clear requirement through the process of
formulation of the given task for increasing the efficiency of the desired outcome for getting
the desired result [14]. The list of software activities which are undertaken for meeting the
requirement of the user are highlighted below:
Analysis of the functional module: The focus should be given on identifying the functional
efficiency of the undertaken project and the requirement plan. The consideration should be
given on the success parameters used for the critical analysing of the undertaken project. The
requirement of the new design and features of the software should be determined so that the
efficiency and the human intervention can be effectively reduced. The durability and cost
associated with the development of software should be determined [15].
Ergonomic phase: The involvement of the human engineering design should be evaluated for
getting the best effective software design. The people should be involved in controlling the
procedure of analysing the required output of the undertaken process. The factors responsible
for the software design should comply the requirement of the user to get desired outcome.
There are challenges in identifying the need and requirement of the stakeholder clearly so that
concise problem statement can be prepared. The active participation of the user should help
in diagnosing the successful module of the software quality standards. The communication
tools should be implemented for getting the clear requirement through the process of

interview, questionnaire, and others. The evaluation of the designing features depends upon
the requirement of the human to increase their operational efficiency [16].
Product Safety parameters: The quality of the software depends upon the product safety
parameters for analysing the efficiency of the undertaken project. The focus should be given
on the sensitivity, confidentiality, reliability, and accuracy of the information. The results of
the calculation should be accurate so that there should be no difference in the completion of
the tasks. The liability of the software depends upon the operational program of the project.
The emphasis should be given on the project outcome process for foreseeing the required end
product of the project [17].
Market analysis phase: The consideration should be given on emphasising the market
analysis program so that the features of the software should be determined. The innovative
ideas can be formulated for identifying the requirement of the project work. The strength and
weakness of the project can be determined by analysing the outcome and expectation of the
project.
Strength and weaknesses of the software: The quality standard of the developed software
should be determined for analysing the strength and weaknesses of the software. The focus
should be given on demonstrating the technical requirement of the undertaken project. The
systematic analysis of the peer to peer steps of the software design process helps in
evaluating the success of the project. The critical decision should be taken by the system
designer for improving the work performance of the stakeholders to take creative decision for
accomplishing the given tasks within the given specific time and cost [18]. The evaluation of
the prototypes helps in analysing the efficiency of the programming code.
Decision phase: The selection of the right methodology for the development process of the
software. The qualitative analysis of the decision process helps in analysing the efficiency of
the product development methodology. The consideration should be given on the
manufacturing process for identifying the profitability of the software process. The
alternative solution should be prepared in relation to the technical failure efficiency [19]. The
incredibility of the manager and system designer for resolving the complexities associated
with the project delivery model. The decision matrix should be prepared for analysing the
impact of each solution and select the best process for the development of the software.
the requirement of the human to increase their operational efficiency [16].
Product Safety parameters: The quality of the software depends upon the product safety
parameters for analysing the efficiency of the undertaken project. The focus should be given
on the sensitivity, confidentiality, reliability, and accuracy of the information. The results of
the calculation should be accurate so that there should be no difference in the completion of
the tasks. The liability of the software depends upon the operational program of the project.
The emphasis should be given on the project outcome process for foreseeing the required end
product of the project [17].
Market analysis phase: The consideration should be given on emphasising the market
analysis program so that the features of the software should be determined. The innovative
ideas can be formulated for identifying the requirement of the project work. The strength and
weakness of the project can be determined by analysing the outcome and expectation of the
project.
Strength and weaknesses of the software: The quality standard of the developed software
should be determined for analysing the strength and weaknesses of the software. The focus
should be given on demonstrating the technical requirement of the undertaken project. The
systematic analysis of the peer to peer steps of the software design process helps in
evaluating the success of the project. The critical decision should be taken by the system
designer for improving the work performance of the stakeholders to take creative decision for
accomplishing the given tasks within the given specific time and cost [18]. The evaluation of
the prototypes helps in analysing the efficiency of the programming code.
Decision phase: The selection of the right methodology for the development process of the
software. The qualitative analysis of the decision process helps in analysing the efficiency of
the product development methodology. The consideration should be given on the
manufacturing process for identifying the profitability of the software process. The
alternative solution should be prepared in relation to the technical failure efficiency [19]. The
incredibility of the manager and system designer for resolving the complexities associated
with the project delivery model. The decision matrix should be prepared for analysing the
impact of each solution and select the best process for the development of the software.
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide
1 out of 27
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
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.