Software Design Activities With Lenses For Engineering Design

Research Aim

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 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 Objectives

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.

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.

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.

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.

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 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.

Research Scope

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 design activities can be effectively done by implementing the framework of engineering practices which are comprised of five phases which are precisely described below:

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].

Research Questions

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].

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].

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 operational functionality and the involvement of the human resources in the completion of the project plan [12].

Research Methodology

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.

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 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 interview, questionnaire, and others. The evaluation of the designing features depends upon the requirement of the human to increase their operational efficiency [16].

Literature Review

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.

Evaluation phase: The impact and the quality standard should be prepared for the developed project according to the requirement specification plan given by the user during the project initiation phase. The rules and regulations should be determined for analyzing the successful acceptance of the project. The outcome of the software quality program should meet the project phase [20].

The designing of the software depends on the following activities to achieve the quality standard of the requirement plan so that the customers need and requirement can be achieved.

The software designing activities are accomplished of series of process which works in the direction of getting the desired outcome and working schedule. The activities which are associated with the development of the required software are comprised of platform information which is used for project initiation procedures and determining the areas of improvement in the working and existing software. The specification of the demand should be forecasted so that the features of the software can be visualized effectively [21]. The description of the data should be clearly defined and prepares a data matrix for the systematic design of the software and its required quality. The architectural design of the software helps in analyzing the parameters and the graphical user interface for the software so that it can be made compatible for using it. The graphical user interface should be developed by analyzing the learning capability of the user. The software should be easy to use so that non-computer user can also use the system effectively. The component required for formulating the software design should be according to the requirement of the project. The efficiency of the project can be improved by aiding new features and communication environment in the software design. The database for the software should be designed for storing the required data and information carefully in it so that confidentiality, sensitivity, and accuracy of the information can be preserved. The effective database can be prepared by combining the result of three phases such as Architectural design, component level design, and graphical user design. The output of the software designing process are the development of the system architecture, identification of the database specification model, getting the specification of the user interface, and systematic development of the component model [22]. The focus should be given on the sequential step of the software programmed designing process. The feedback should be collected from the user for the improvement of the software design model.

The cognitive process should be laid down for taking effective decision to understand the problems and vulnerabilities associated with the software development process. The effectiveness of the software depends upon the systematic analysis of the software design techniques and context switching program. The efficiency of the software design development process depends upon the decision making capability of the system designer. The effectiveness of the software depends on the quality standard used in the development of the design process. The central focus should be given on the designing and development phase of the software process [23].  The software engineering practices should be deployed for getting the required result from the proposed project initiation phase. The transparency should be incorporated in the software activity schedule to systematically analyze the difference in the working project. The success of the software depends on the innovative ideas developed in the undertaken project. The efficiency of the software design depends upon the aspect and acceptance of the project model. The component of the software should be separately programmed so that error rates in the project process can be reduced effectively. It helps in minimizing the impact of vulnerabilities and uncertainties associated with the project development phase. The designing process can be accelerated by giving emphasis on the component level designing process so that required changes can be easily done. The fruitful results of the software development process can be achieved by analyzing the product requirement specification process. The significant changes should be incorporated in the design phase for increasing the functionality of the product design [24]. The continuous improvement program depends upon the decision making capability of the system designer to develop the software according to the expectation of the users. The visualization of the end product should be measured for analyzing the quality standard of the project design. The scheduling of the software designing activities should be systematically laid down with the association of resources and cost required for completing the given tasks.

The software design activities are comprised of several challenges which results in the inefficiency of the software development phase. The scheduling project is accompanied with challenges like change in the requirement and demand of the user, inefficiency of the designing process, inefficiency in developing the effective quality standard, lack of distribution of resources in completing the specified tasks, innovation and change in the marketing trends, inefficiency of the human resources in completing the given tasks, inaccuracy in the data collection process and others [24]. The challenges in the software designing phase are described below in detail:

Change in the requirement of the software features: The changes in the marketing trends and innovation in the technologies compels the user to change and modify it requirement plan. The incorporation of the changes during the project development phase is the typical tasks because it will affect the later development software activities. The designing and development process of the software are interdependent to each other. The delay in one activity will result in increasing final deadline of the project. The software design principles should be determined to resolve the complexities associated with the project [25].

Process design: The software development process is not designed according to the requirement of the project. The focus should be given on balancing the cost and the time factor for the successful completion of the project. The broadcasting of the problem is the major challenge to get effective solution for the development program of the project. The change in the supporting activities will create the problematic scenario of the system design [26].

Change in Technology: The innovation in the digital technology and new marketing trends is the major challenge to develop the software innovative to the existing software. The inclusion of new technology during the designing phase creates problematic scenario. The software designer does not emphasis on the analyzing of the new marketing trends in the field of technology.

Ethical Issues: The ethical code of conduct is not properly laid down by the system designer during the project completion phase. The project is not able to meet the customer requirement because the software designer does not give emphasis on the customer participation in the software development process. The consequences of the ethical issues should be measured [27].

Changes in the software design: It is difficult to change the undertaken software design because the data and process is scheduled according to the requirement specification plan provided by the user during the project initiation phase.

Contribution and efficiency of the human resources: The success of the software development process depends upon the efficiency and credibility of the human resource in the software process. The operation efficiency of the stakeholder helps in visualizing the quality of the end product.

Systematic arrangement of the organization hierarchy: Lack of flow of information and scheduling of communication can create a problematic scenario for the development of the software. The availability of the resources during the demand placed by the stakeholder should be made available to resolve the problems of resource distribution [28].

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 design planning helps in identifying the clear idea of the project scope, identifying the key designing model for the software, prioritizing and setting of the design problems. The problem space decision helps in analyzing the problems and formulating the problem in an effective manner. The active participation of the customers should be taken for analyzing the problem and formulating it required design to resolve the vulnerabilities accompanied with the programming model. The solution space decision is comprised of three processes which are classified as generative effective solution for formulating the problems, evaluating the efficiency of the solution, and selection of the best alternative solution [29]. The decision road map should be constructed for developing an effective design for the forecasted model.

The analysis of the literature review helps in finding the challenges and the software design activities. The central focus is given on incorporating the engineering management principle for developing the effective software activity schedule. The operation view of the software should be forecasted by visualizing the quality of the end product. The approval of the software requirement specification should be taken by the users for scheduling the software development activities in the direction of the project requirement. The construction of the decision road map helps in taking effective decision for selecting the right choice from the prescribed alternatives. The construction of the decision road map is comprised of three activities which are stated as concern of the software design, taking effective decision according to the requirement plan, and lastly measuring and visualising the end product of the undertaken software project [30]. The planning of the design should be done according to the project scope and objectives so that the success criteria can be met. The work schedule of the team members should be divided so as to manage the resources among them for completing the given activities. The parameters which are specified for measuring the design approach and estimation of the problem should be according to the given tasks and working schedule of the software development life cycle. The focus should be given on time dependency in the completing the software structure of the given program. The model view controller (MVC) should be placed for analysing the performance of the developed software. It helps in estimating the quality standard and the end result of the undertaken project [31]. The systematic view of the design structure should be constructed for determining the impact of major and minor activities incorporated in the development process of the project. The work efficiency of the team members should be measured for analysing the time required for completing the software development process. The engineering principles should be accompanied with the software development process for increasing the efficiency and effectiveness of the working scheduled procedures. The sequence of activities should be generated by implementing the model view controller for improving the work efficiency and planning of the software architecture. The designing and identification of the problems and vulnerabilities associated with the software should be clearly examined for developing an effective formulation of the problems. The effectiveness of the decision depends upon collecting the data and information from various sources to design a software architecture to fulfil the requirement of the users. The program should be designed for overcoming the challenges and problems associated with the development process of the software. The central focus should be given on determining the requirement of the user in the clear and precise format so that in discrepancies associated with the development process of the software can be avoided at high priority.  

The software design which is developed by applying the principles of engineering design principles are convergent in the process architecture. The central focus is given on the process laying down to resolve the complexities and vulnerabilities associated with the software development program. The sequential series of steps should be designed for formulating the design solution for the undertaken software project. The analytical approach should be given emphasis for constructing the software architecture. The developed software solution should resolve the requirement and expectation of the customers in an effective manner [32]. The ethical code of conduct should be deployed for determining the software design. The control architecture and the system mapping should be done for increasing the impact and quality of the developed software because the mapping process helps in managing the balance between the software requirement and the computational software design architecture. The software requirement focuses on different levels such as analysing the functionality and features of the software, determining the constraints associated with the development process, analysing the acceptance and exception condition forecasted with the software process, analysing the management of the interactive devices, and evaluating the efficiency of the user action plan. The computational implementation of the engineering practices in the software designing activities helps in developing the control architecture for the required schedule, developing the effective computer architecture program, designing of the algorithm and activity schedule, development of the data structure, and designing of the software schema to analyse the quality of the end product. The clear format should be laid down for determining the functional domain of the system architecture program [33]. The interdependency of the functional components should be checked for managing the flow of information to enhance the working capability of the developed software. The activities should be scheduled for determining the level of complexities and uncertainties associated with the systematic development of the software. The efficiency of the software depends on the user behaviour because the change in the requirement plan results in increasing the compelxities and difference the end result as expected by the user. The creative skills of the project manager helps in incorporating the trends and technologies evolved in the global market to improve the architecture of the software in an effective manner. The volatility in the requirement changes increases the burden on the software designer and also there may be the chances of overrunning of time and cost approved for the undertaken software program. The emphasis should be given on customer perspective view and the designer perspective view equally so that the proper balance can be created between the two and the quality output can be received which is capable of fulfilling the expectation of the customers without any overburden on the system designer.

The application of engineering design principles on the development  process of the system design is comprised of benefits and advantages because it helps in finding out the root cause analysis of the failure of the existing software, focuses on the gaps and flaws, emphasis on area of improvement, and others. The incorporation of the engineering principles helps in making the software design simple and adequate which can be easily understandable by the computer users and non-computer users. The value of the project can be determined by analysing the functional program of the software. The efficiency of the process should be determined for analysing the impact on the user based on its performance. The design of the software should be simple so that the programmer can effectively developed the project. The focus should be given on the threats and risks associated with the software so that the conceptual design can be effectively developed. The success of the software depends on the clear vision of the software execution and programming capabilities. The software design activities are the blue print of the project outcome process. The software process should be clearly defined a systematic view of the requirement specification plan. The architecture of the software depends on the strategic decision which should be taken for determining the architectural design of the software model which has the capabilities of managing effective interface in the developed software [33]. The expansion of the software depends upon the undertaken framework to initialization of the process model. The right programming paradigm should be chosen for the development of the software process. The object oriented approach should be undertaken for the development of the designing principles. The uniformity and integration helps in determining the coordination among the designing components. The flexibility in the software design helps in improving the refinement and abstraction process for the improvement of process design. The conceptual error and human error can be reduced effectively by giving emphasis on determining the requirement specification plan so that the compatibility of the software can be improved to meet the expectation and requirement of the stakeholders. The active participation should be take place so that the problems and vulnerabilities can be effectiveness minimized. The programming code of the software should be reused so that the time of the programmer can be reduced. The functional dependencies of the software process should be clearly identified. The communication should be clearly defined among the stakeholders so that the program and software activities can be effectively determined. The modularity of the project helps in increasing the quality of the systematic approach to get specific desired result and functionality of the software. The continuous improvement plan should be developed so that the required changes can be incorporated in the software program to meet the expectation of the customers. The reusing of the software code helps in reducing the time and cost approved for the development process. 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 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 mitigation plan should be developed to overcome the challenges which are incorporated in the development process of the software model. The alternative plan should be prepared for initializing the changes in the functional efficiency of the developed program. The software activities should be scheduled so that flexibilities in the process can be effectively laid down. The quality risks can be reduced by indulging the quality standards and control in the process architecture of the software program. The process methodology should be deployed according to the requirement specification plan developed by the user during the project initiation phase. The valuable functionality can be induced in the development program of the software.

It is advantageous to incorporate the engineering design principles in the software designing activities. The flexibility in the software design process can be easily implemented so that changes and marketing trends can accompany with the developed model. The software project methodologies help in building effective team management program for improving the function module of the developed software. The project can be released earlier than the scheduled time. The transparency should be created between the working process of the software. The new innovative ideas can be created by having an effective coordination and cooperation among the stakeholders and team members. The root cause of the software discrepancies can be effectively analysed by having communication between the functional activity schedule of the software process. The feedback and reviews should be collected for analysing the satisfaction level of the customers. 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 fruitful results of the software development process can be achieved by analyzing the product requirement specification process. The significant changes should be incorporated in the design phase for increasing the functionality of the product design.

The finding and analysis of the literature review helps in defining the efficiency of the implementation of engineering practices on the development process of software activities. The good design should be developed for resolving the complexities and vulnerabilities associated in the existing architecture of the software model. 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. The central focus should be given on determining the facts and figures related to the software design process because it helps in generating an effective design for the required demand placed by the user in the project initiation phase. The contradictory approach should be deployed to analyse the variance in the actual output and the demanded output of the undertaken software. The tendency of the customers is to incorporate changes in the scheduled processes of the project development plan. The flexibilities should be deployed in the software designing activities program. The attention should be given on determining the problems and gaps to incorporate the required technology in the systematic development process of the software. The decision process helps in determining the best software model for developing an effective and required system. The success criteria and quality standard should be developed for getting the required output. The preparation of the documentation is an important step for developing continuous improvement plan. The specific verification and validation protocol should be developed for initializing the required architecture. The visualization of the future result should be measured to check the development program of the software. The dependency of the project activities should be determined for getting an effective and required result of the undertaken process. The expansion of the designing activities should be done for resolving the complexities of the undertaken software development process. The preliminary design of the software should be developed for designing the final result of the undertaken software program. The efficiency of the system design depends on the synchronizing the software designing activities. The analysis of the software solution should be tested on the user performance and behavior to manage the changing need of the customers. The evaluation of the prediction model helps in improving the quality of the undertaken project. The empirical development of the software design depends on the management of the behavioral variable which depends upon the change in the requirement specification plan. The contrasting of the alternative solution helps in determining the architectural design and requirement of the software model. The focus should be given on synthesizing the demand of the software program. The evaluation of the system can be done by analyzing the coding and programming functionality to meet the demand raised by the customers. The software designing activities helps in defining the proposal of the new software model to meet the marketing demand of the project. The clarification of the system requirement emphasis on determining the problem domain and constraints associated with the development architecture of the project. The focus should be given on defining the new ideas for the development of the required architecture of the software model. The justification should be presented for selecting the particular method because it helps in contrasting the characteristics of different alternative solution. The feasibility analysis of the developed software model and the requirement specification plan helps in analyzing the variance in the project outcome. The backtracking of the problem domain helps in emphasizing the project requirement in the clear systematic manner and the required changes can be incorporated in the project start-up phase so that the required outcome can completely satisfied the demand and expectation of the users. The contradictory table should be developed for analyzing the difference between the problem domain and the solution space of the software process. The challenges and problems which are associated with the software program are change in the requirement plan. Communication risks, process design risks, ethical risks, and underpinning of the employees to complete their given tasks. The solution space focuses on determining the mitigation strategy to minimize the impact of challenges in the development process. The change in the requirement plan can be resolved by back tracking the problem domain specified by the customers and users. The communication risks can be resolved by developing an effective communication plan to systematically analyze the coordination between different project activities and stakeholders. The ethical risks can be resolved by deploying the ethical code of conduct during the working hours of the project development program. The training and development program should be arranged for the employees to enhance their skills and talent to optimize the software performance in meeting the requirement of the user. The project activities should be prioritized for getting the required result of the project model. The application of the software helps in improving the functionality of the human resources. It helps in reducing the human error. The designing prinicples helps in exploring the project requirement in the systematic manner. The focus should be given on defining the comparison between engineering design and software design. The scope of the project design can be effectively improved by deploying the engineering practices to develop the quality software which is capable of meeting the functional requirement of the user. The systematic organization of the problem domain helps in expanding the project scope and objectives so that the clear specification of the requirement can be generated. The engineering design principles helps in implementing the feedback loop for determining the gaps and flaws in the developed software model which makes its incompatible to meet the requirement and opens door for areas of improvement. The data should be collected in the field of determining the project objectives. The poor construction of the problem domain results in the failure of the software design and its component level design. 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 continuous improvement plan of the software model should focus on analyzing the feedback loop of customer reviews for improving the functionality of the developed software.

Conclusion

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 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. The Empirical study of literature review for analysing the facts and figures related to the software development process. 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 major factors which are responsible for designing the software design specification are goal, requirement matrix, and innovative ideas and features required in the software functional program. 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. 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 unclear requirement specification plan results in the poor quality of the outcome and software fails in meeting the requirement of the users. 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 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 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. The output of the software designing process is the development of the system architecture, identification of the database specification model, getting the specification of the user interface, and systematic development of the component model

References:

[1]M. Avital, K. Lyytinen, R. Boland, B. Butler, D. Dougherty, M. Finout, W. Jansen, N. Levina, W. Rifkin, J. Venable, “Design with the positive lens: An affirmative approach to designing information and organization”, International conference on communication of the association for information system, vol. 18, pp. 519-545, 2006.

[2]O. Gabry, “Software engineering-Software process”, 2017.

[3] S. Kristensen, and M. Babar, “Comparison of problem solving from engineering design to software design”, International conference on design engineering, 2012.

[4]R. Adams, S. Daly, L. Mann, and G. Alba, “Being a professional: Three lenses into design thinking, acting, and being”, 2011.

[5]S. Khandani “Engineering design process”, 2012.

[6]L. Anderson, “Information sharing in distance collaboration: A software engineering prospectives”, 2013.

[7]W. Scacchi, “Process models in software engineering”, 2001.

[8]W. Phuwanartnurak, “Exploring the use of Wikis for information sharing in interdisciplinary design”, 2013

[9]W. Scacchi, “What does It mean to design? A qualitative investigation of design professional experience”, Journal of engineering education, Vol.101, No. 2, pp. 187-219, 2012.

[10]C. Mortberg, and T. Bratteteig “Methods that matter in digital design research”, 2013

[11]S. Easterbrook, J. Singer, M. Storey, and D. Damian, “Selecting empirical methods for software engineering research”, 2013.

[12]V. Vaishnavi, Kuechler, B., Petter, S, “Design science research in information systems”, 2013

[13]K. Biesialska, Franch, X. and V. Mulero, “Protocol and tools for conducting agile software engineering research”, 2015

[14]J. Donnell, “Gifts to the future: Design reasoning and design researvh and critical design practitioner”, 2015.

[15]B. Kitchenham, Carn, R, “Software design methods and tools”, 2013.

[16]R. Taylor, and A. Hoek, “The once and future focus of software engineering”, 2013.

[17]J. Logren, “Applying design methodology to software development”, 2013.

[18]F. Queiroz, R. Silva, J. Miller, “Good usability practices in scientific software development”, 2013.

[19]A. ALturki, and G. Gable, “Validating the design science research roadmap”, 2012.

[20]A. Tang, ans A. Aleti, “What makes software design effective”, 2012.

[21]M. Segalwitz, “Participation in participatory design research”, 2012.

[22]M. LaMantia, Y. Cai, MacCormack, A. ,and J. Rusnak, “Evolution analysis of large scale software system using design structure matrices and design rule theory”, 2012.

[23]J. Lowgren, “Applying design methodology to software development”, 2012.

[24]P. Barthelmess, K. Anderson, “A view of software development environments based on activity theory”, 2014.

[25]Z. Wang, B. Li, Y. Ma “An analysis of research in software engineering: assessment and trends”, 2016.

[26]A. Kumeiga, B. Vilet, “A software development methodology for research and prototyping in financial markets”, 2011.

[27]J. Waldo “On system design”, 2006.

[28]B. Curtis, H. Karsner, N. Iscoe, “ A field study of the software design process for large system”, 2016.

[29]M. anjum, and D. Budgen “An investigation of modelling and design for software service applications”, 2017.

[30]M. Petre,  “Discipline of innovation in engineering design”, 2014

[31]A. Messac, and W. Chen “The engineering design discipline”, 2015.

[32]K. Gericke, and L. Blessing” Comparison of design methodologies and process model across disciplines: A Literature review”, 2011.

[33]F. Bashier. “Design process system and methodology of design research”, 2013.