Waterfall Methodology
> The enrollment system can come in many ways depending on the school in question. Using the waterfall method, we need to make sure of the requirements and plan the sequence of the transaction. First we will identify what are the students required to do before enrolling. Do they need a birth certificate? Do they need a 2x2 picture? After this particular process what are they supposed to do next? That is what we will need to figure out in the requirements process.
After which is the designing, it can first be a prototype of a framework that portrays the systems methods and processes one after another. After the designing, we would naturally go to the coding phase which can be divided into 2 parts: Coding & Debugging. Depending on the testers, this process may repeat until the system is functioning as the users would want them to but since this is a waterfall model then it might not be the case as the waterfall model is designed specifically to do the processes step by step without the need for going back.
And lastly we have the verification; since the debugging stage is done during the development process then it is now ready for the verification process. Should the verification process turn out acceptable for the users then it is possible that the developed system is already to be implemented. However if its not then the WHOLE process needs to be started again. After a successful verification, the system is now implemented, maintained and in most cases updated for the better service for the users.
SCRUM Methodology
> The SCRUM Methodology is a team effort method so it is only natural for it to have 2 or more members. With this said, for a simple enrollment system the following staff might be required for developing this system
1. Team Leader
The team leader is in charge of organizing the team, it might even be better if the leader had background knowledge in all of the possible roles of the SCRUM team so that he can manage the team well and guide them throughout the process. The team leader is also the one that, in most cases knows the company and the system that it wants to be done.
2. System Analyst
The system analyst is responsible for identifying the requirements, processes and transactions required for the system. In this case, the system analyst should know the basic process of the enrollment system as well as the other possibilities such as irregular students or transferees. Basically, whatever the analyst has gathered will be the heart of the system making them a very vital part of the development of a system.
3. Programmers
The programmers are the body and mind of the system, with the data gathered from the system analysis they create a system to provide the people. These ones are responsible for the making of the system itself with the help of a few people especially the testers.
4. Testers
These people are responsible for checking the systems for potential errors that may either harm the users or crash the system. Testers are the most important members of the team since they are mostly the ones that uses the system. What they say is what the programmers usually debug so that the system becomes perfect for the company. Also, these people usually work in the company that you are making the system for.
If the team execute the task given to them then they may develop the best software possible for the company. There are also other part of the team but they may be to be not part of the development team. These people are
- Product Owner
- Users
- Personnel
No comments:
Post a Comment