Week 3: Finding out Systems Requirements

The lecture was about requirement gathering and the skills to find out what we need. In the SDLC phase, we are now in the analysis phase. This is where the system designers sit down with the users or owners of the systems and figure out what are their needs and wants. There are two methods when introducing a new system, briefly explained as either the system wraps around the users or the users adapt to the new system.

The first is not replacing the current work process but just digitising or making it simpler or faster. The new system would produce better effiency from the users.

The other method is replacing certain business processes and streamlining them. Users have to be retrained to use the system. Simply put, the users revolved around the system.

Also we discussed in the lectures about how to ask questions on getting the requirements of the system. If the requirements are not gathered properly, the system might have conflicts with the users or the business process. Also reviewed together with the questions are the paperwork that are used currently. Do we duplicate them in the new system or do we need to redesign them to fit the system?

Joint Application Design(JAD) were highlighted near the ending. A JAD is where the users or stakeholders of the system sits down together with the project team members. Certain resources must be available such as an overhead projector, whiteboard, printer, etc. The sessions' minutes are taken down and documented in case. This would continue the flow of events and even documentation would be easier at the end of the project.

That is about it... My next post would be about my revision on the topic. Most probably would be a review of the questions i would have on hand before i enter the tutorial for the interview.