Individual Critical Reflection Report

Individual Critical Reflection Report

This individual report provides a clear description and justification of the modeling decisions that were taken as well as a reflection on how the models relate to each other and the potential strengths and weaknesses of the team’s work. The paper covers the two models which are the requirements model and the analysis/ design model and why it was important to correctly determine when and how to transit from the former model to the analysis/ design model.

WRITE THIS ESSAY FOR ME

Tell us about your assignment and we will find the best writer for your paper.

Get Help Now!

Description and justification of the modeling decisions

The systems requirement model

Turban (2013, p40) claims that the system requirements model entails what the system in its entirety is required to do. It may be broad and high level or more specialized and detailed depending on the type of processes in question. The group chose the detailed requirement because it allows for organization into hierarchy that culminates into highly efficient processes. This was important because it helped the group meet high level requirements in the design and functioning of the process. In so doing the group was able to manage the complexity of large systems although we found it necessary to be more careful while moving to the design/ analysis model e in order to minimize on errors.

The group realized that the systems requirements model had a few shortcomings like it at times fails to meet the requirements of the user and this may go undetected until the system is integrated, when this happens, it leads to unnecessary inconveniences in terms of both time and resources. Additionally, the model has a relatively longer than the desired development cycles. The fact that requirements change so quickly with advancements in technology and other related factors often render the systems requirement model unsuitable because of the high costs incurred during upgrades for the system to meet the new requirements (International Workshop IW-SAPF-3, & Linden, 2001, p53 & Satzinger, Jackson, & Burd, 2008, p59). It was always challenging to decide when to transit to the design/ analysis model owing to the various shortcomings that are encountered at the requirements model level.

The analysis / design model

Casteleyn (2009, p43) asserts that the objective of any model is to support the efforts of the architect in making the project to have the right design, specification and decisions in order to achieve the intended goals. The right design and specification is often assessed using denominators like business viability, customer satisfaction, meeting the constraints of the project and the associated risk levels. For the designer to be able to meet the required standards, he or she needs to work with sufficient credibility, accuracy and working range. In essence the analysis/ design model is an improvement on the requirements model as it relies on it in generating information like customer preferences, market trends and the industrial characteristics. Once the requirements stage is well orchestrated, then the analysis/ design model will be more efficient owing to the reduction in errors (Wasson 2005, p89). The reverse is also true as inefficiencies in design leads to errors being carried forward to the analysis/ design stage.

Issues and limitations

A good model should be able to detect any defects early in the life cycle of a product. As such testing should be carried out as early as possible in order to minimise the costs of repair. This implies that testing should be integrated in the design of the system so that it can be verified against the requirements as early as possible. This is the basis on which the requirements model works as it understands and outlines the set of requirements in advance. As earlier outlined, the m…………………………………