Download Software Engineering: Implementation Planning, Affinity Analysis, and CPM and more Exams Software Engineering in PDF only on Docsity!
Discussion Assignment With such questions, I always begin by defining the terms of reference in order to have a better understanding, and in this case we have “implementation planning, and affinity analysis” as the main terms of reference. Following the discussion exercise, I have broken it down into four (4) different questions as follows: a) Discuss the effect of implementation planning and reason the role of affinity analysis on reengineering effort. b) What results are based on affinity analysis? c) Discuss why cost and schedule estimates are done before detailed requirements/design analysis? d) When, do you think, can these be estimates be postponed to a later stage of software development? Before responding to each of these questions, I will begin with the definition to each of these terms as follows: Implementation planning: This is one of the most commonly used strategic tools that aims at breaking the strategy into smaller identical steps, allocates resources to it and suggests the road map on a company can obtain its goal and mission (Conger, 2008, pg.140) Affinity analysis: On the other hand, this is the act of bringing business processes together by the closeness of their functions or activities based on the data entities they have or share in common (Conger, 2008, pg.133, 801). Having understood the above expressions, I can now comfortably provide answers to all the four different questions as follows:
The effect or outcome of “implementation planning” are very effective positively for reengineering effort as it helps to eliminates errors by creating a road map that facilitates how an organization can attain their recommendations. For example, it develops job descriptions, defines the organization, plan information technology, plan trainings, and finally plan the implementations (Conger, 2008, pg.140 - 142). Now, the role of affinity analysis here is to make sure that it brings all the business processes that share common data entities together just as stated in the definition above (Conger, 2008, pg.336). I think that in my opinion the results that are based on affinity analysis are processes from the process hierarchy and data entities from entity relationship diagram because it is these statistics or results that affinity analysis analyzes to get normalization across the organization (Conger, 2008, pg.133-134). In my opinion, the reason as to why cost and schedule estimates are done before detailed requirements/design analysis is simply to ensure that the required statistics are available in order to avoid future change which may affect the organization negatively as new updates, training, etc. are required (Conger, 2008, pg.744 - 745). When the estimates are identified of weaknesses as a result of errors, then it can be postponed. NB: Word Count = 436
References
Conger, S. (2008). The New Software Engineering. Retrieved Thursday 14th^ November, 2019 from: https://learn.saylor.org/pluginfile.php/235273/mod_resource/content/3/Conger- NewSoftwareEngineering.pdf
Define history processing. Define screen contents and process flow processing. Define error messages/abort processing. Define end of day, audit trail, Trans Log. Review requirement with Vic. Mary: Define customer maintenance. Define video maintenance. Define backup and recovery requirements. Define startup/shutdown processing. Define file purge, history file creation not done in rental. Document all requirements in PDFD, ERD, DD. Review requirements with Vic. (Cogner, 2008, pg.191) But then, the appropriate activity sequence established for the CPM exercise are: Provide add, change, delete, inquiry functions for Interactive processing and date display for all outstanding video rentals, including fees owing On-line processing from 8am to 11pm daily. The maintenance of customer, history of rentals, rental history for each video tape, creation, and On-line, Off-line Computation of late fees owing from prior transactions. The ability to create new customers as part of The ability to add few videos to the system as part On-line, Off-line, Minimize data entry in rental processing by using Provide transaction logging for database integrity. Do daily backup of all files and application programs. Provide ad hoc reporting capability for all files and only with another package (Cogner, 2008, pg.167).
NB: Word Count = 582
References
Conger, S. (2008). The New Software Engineering. Retrieved Thursday 14th^ November, 2019 from: https://learn.saylor.org/pluginfile.php/235273/mod_resource/content/3/Conger- NewSoftwareEngineering.pdf Supporting Planning and Control: A Case Study : Retrieved Thursday 21st^ November, 2019 from: https://my.uopeople.edu/pluginfile.php/590870/mod_book/chapter/208552/PERT%20CPM%20for %20Project%20Management.pdf. Project Scheduling: Retrieved Thursday 21st^ November, 2019 from: http://www.math.csusb.edu/faculty/prakash/611/Project_Management.ppt.pdf Learning Journal Fon Roland Achu University of the People Rental/Return Processing Relationship Video Maintenance Backup, Recovery Requirements Conversion And Training Requireme nts Document all requirements ERD, DD^ in PDFD, Define Startup / Shutdown Processing End of day, audit trail, Trans Log Error messages/ Abort processing Purge /History File Creation Not Done in Rental Screen Contents and Process Flow Customer Maintenance
I am very positive and encouraged to as I look forward to proceed with unit 3, since as a good self- directed learner I am enthusiastic in getting the best out of this course. I know by the end of this course, I must have gain some skills which will be peculiar in my field of I.T. I have noticed the importance of the role of a project manager in the developing of applications in this unit 2 exercises. One of the ways to apply these ideas and concepts gained to my own experience is by carrying out constant practices with different exercises from the text and the internet, and also to make sure that I try explain the concepts of each unit I have learned to anyone who is willing to be of assistance to my study. I would appreciate the approach and methodology of the instructor especially if supplementary lecture videos links are provided help some of us understand better the concepts we are being thought. Summarily, as of now I can say that software engineering is all about identifying a problem, come out with the solution and then design the blueprint for the software to be programmed. To attempt this question, I would like to define the terms of reference which are “algorithmic, function point, and combined top-down, bottom-up.” Below are the contextual definitions of these terminologies: Algorithmic , is simply a method or technique that relies on one or more key formulae that is used to develop and estimate the necessary power for a project work; examples of such algorithmic techniques include linear, multiplicative, analytic, tabular, and composite (Conger, 2008, pg.173). Function point , is also another method or technique that is used to obtain estimate for an application type, based on organizational history approach. That is, to get an estimate for one function point per application type, the baseline number of the function point is divided by the actual cost/time for the development of the application (Conger, 2008, pg.180). Top-down , is an estimating technique that combines one or more of the other techniques or methods to deduce a time estimate of a project by using the properties of the project following the 40-20-
rule. The rule states that 40% of the estimated time is used for analysis and design, 20% is used for coding and unit testing, while the remaining 40% is used for project testing (Conger, 2008, pg.179). Bottom-up , is also an estimating technique but it follows the opposite views of the top-down application approach. Here, the person to do the development is responsible for identifying and estimating each software component cost such that the costs are combined to come out with the estimated cost of the overall project in question (Conger, 2008, pg.180). Having understood the above mentioned estimating methods or techniques very well, I can now proceed by looking at their advantages and disadvantages, compare them and come out with my conclusion. Below are the advantages and disadvantages of the given estimating techniques (Conger, 2008, pg.174): Algorithmic Estimating Technique Advantages
- It is able to generate repeatable estimations.
- It is easy to modify input data, refine and customize formulas.
- It is efficient and able to support a family of estimations or a sensitivity analysis.
- It is objectively calibrated to previous experience. Disadvantages
- Poor sizing inputs and inaccurate cost will result in inaccurate estimation.
- Does not accommodate exceptional circumstances.
- Assumes history predicts future applications.
- Some experience and factors cannot be easily quantified. Function Points Estimating Technique Advantages
- May overlook system level complexity and costs.
- Requires more effort than most other methods. Conclusively, there are so many different useful methods of project estimating which have not been included in this exercise, some of which are expert judgment, analogy, CoCoMo, function points, top-down, and bottom-up as compared above. Note that, all of the existing methods have both advantages and disadvantages, but a method or technique is preferred depending on the developer and the kind of project in question (Conger, 2008, pg.181). NB: Word Count = 1168
References
Conger, S. (2008). The New Software Engineering. Retrieved Thursday 14th^ November, 2019 from: https://learn.saylor.org/pluginfile.php/235273/mod_resource/content/3/Conger- NewSoftwareEngineering.pdf
