Software design

In this stage we draw necessary diagrams of system.

We draw Use case and ER – diagram to our system. We also make some UI prototype to show    customer and get feedback from customer. 

E-R Diagram

 

USE CASE Diagram

 

In this stage we got some decision according to ACM PRINCIPAL 4 guidelines.

 

Example:

 

4.05 Disclose to all concerned parties those conflicts of interest that cannot reasonably be avoided or escaped.

 When several parties engaged in a project conflicts are normally happen. Sometimes these conflicts of interest cannot avoid. Therefore it is a responsibility of software engineer to inform about those conflicts to concerned parties.

In this system if any conflict arise we are responsible for inform all concerned parties about it. As example when we developed this software the client required to keep the student details a. But the required data base size is not sufficient to keep all the data of each and every student, then conflicts of interest was arising.

So after we discussed us can get agreement only keep back up one year when student leave the system. I think this solution is temporary decision. They are agreeing keep their file tally with system in first year. If system was more efficient they agree to pay attention to expand database.