The practicum course on Systems Analysis and Design, has been effective in providing me with a nuanced perspective on the implication of System Analysis and Design. Initially, the term System Analysis and Design was conceptualized as a broad term for describing methodologies involved in high quality information system maintenance and development; for me it involved the procedures to get something done within the larger software ecosystem. But this definition was a vague understanding into the processes that define the complex system and environment of a software. Software as a tangible product can be tailored to fit a client’s need and requirements. In cases where they are deployed to a larger ecosystem and are central to the client’s work, they may be many moving part, that are all in a way connected to the other, and cannot be avoided. But like all system, they require maintenance and upgrade. This course has allowed me to see and evaluate on the modes and procedures that could be deployed to ensure the upgrade is accomplished without necessarily inconveniencing the whole system.
An underlying factor that has been constantly outlined during the practicum is that the fundamental technological changes and advances subjected to a system, may be so frequent and rapid that experiences of one functional product, may not necessarily be applied in others. This is very constraining to developers especially in a complex combined system. As such, there is a rising need for efficiency. The constraint, as outlined in the course come in triples, they include time, cost and quality constraint. Roth et al (2014) outline that “creating high-quality information systems that meet expectations and provide meaningful value to organizations is a much more complex endeavor”. All of the mentioned constraints if not attended to before hand and properly planned may work to create conflict, which effectively slows down any shot at progress. There are several factors both internal and external that impact the triple constraint mentioned. These factors can be costly to any company, as such, there is a need for the formulation of a good software project management framework to work in holistically guide a team or groups of teams involved in upgrading a system. This is essential for a quality and well budgeted software.
System Analysis and Design (SAD), describes the methodologies involved in developing high quality Information Systems, which effectively combine IT, people and data to support a business’s requirements. It is a roadmap that caters and predefined the process to mitigate against all hurdles by first identifying them then defining how to prevent or overcome them. The planning phase is particularly he most important phase in SAD, as it defines and provides a general roadmap and schedule to task accomplishment. As the more fundamental process it involves a two step process of understanding why the information system in question should be developed and creating an elaborate framework of how the project team assigned will develop and implement the discussed agenda in a timely and cost efficient manner.
I believe the Planning phase, to be superior to the Analysis phase since it elaborately creates values and assigns importance in matters before hand, to prevent losses. It critically provides the project team assurances that the management overseeing the project will support the proposed system change, and evaluates whether the changes will work and be feasible in the current organizational environment. Planning starts by outlining a problem and providing the justification to the management and stakeholders. It lists the requirements and project objectives, defines the project scope, and outlines all deliverables and estimated due dates. With all this in mind, it provides a detailed project schedules, outlines the potential risks and the management plans to mitigate the risk. It finally defines the roles and responsibilities of each party.
In my future line of study and work, the Planning phase as outlined will allow for better project management. This is because it will provide leadership that is close to the vision and motivation, eliminating potential roadblocks, and foster an attitude of accountability. This allows the team to analyze the effects of the problem and how the solution will affect the user. Studying this course, as such, becomes handy when evaluating a need for software change, how change will be effected and how the modification comes to affect the whole ecosystem at large.
System Analysis and Design is an exciting and active field, that provides developers with new techniques and approaches to change in a complex and active software ecosystem. Its main aim is to establish effective and efficiency in the process of change. All information system move through four critical phases, these phase include planning, analysis, design and implementation. In my experience studying this practicum, the planning phase is the most important and should be the most emphasized. When well executed it ensures better and timely development. As a system analyst I will be encouraged to plan holistically so as to deliver in time and on budget, as SAD emphasizes.
Roth, Alan Dennis, Barbara Haley Wixom, Roberta M. (2014). “Systems Analysis and
Design”. VitalSource Bookshelf, (6th Edition). Wiley Global Education US, web.