Requirement gathering

We met our client and his basic requirements were record student and staff details and quickly search them. So, we thought how to do our work professionally. We recorded several things and met other related professional persons to get their experiences. We think who are directly interacting with the system. 

According to our decision principal, class teachers and clerks may be directly interacting with our system and students also can be interacting with system.  In this case we follow ACM PRINCIPAL 2 guideline to give best service to client.

We note down what details we should record our system. Within this discussion we can take good knowledge about our software domain.


Example :
  
2.01 provide service in their areas of competence, being honest and forthright about any limitations of their experience and education.

According to code of ethics Software engineers should be honest about their knowledge. Client may come up with various requirements. As they are non-technical people they don’t have idea about implementation process. Therefore when client asked for something, developer should be honest to accept the limitation of their experience and education while provide service in their areas of competence.

When we developed this system our client requested to implement image recognition functionalists. But as developers, we don’t have proper knowledge this area and we honestly accept our limitations.

In the initiate stage we inform the client that we are undergraduates and don’t have industry experience. When we developed the Student Management system, we provided better service to the client by using our knowledge on areas that are competence to us.