Principle 3: PRODUCT

Software engineers shall ensure that their products and related modifications meet the highest professional standards possible. 

In particular, software engineers shall, as appropriate:

3.01. Identify, define and address ethical, economic, cultural, legal and environmental issues related to work projects.

Since our project was related to financial area, we had to contact even Central Bank to get advised about the legal concerns regarding our project. Also economical and ethical issues were came across since we were developing this mostly for the foreign users. We had considered and contacted most of the related parties and we were aware about most of the things we needed to know.

There was some legality issues with our application data that we were concerned about. There was no application like our application in the market, and most of the clients were afraid to give data t our application since it was risk loosing customers and threats from the money sharks.

3.02. Ensure that they are qualified for any project on which they work or propose to work by an appropriate combination of education and training, and experience.

We were sure that we were mostly capable for developing this kind of a project which was very new for us but we had the experience we needed in java programming and education about doing projects in a professional manner. So the working process was easy for us we had the elements we needed.

Our combination in experience was good. We had good java knowledge, XML knowledge, and Mayura has been used IDE's before for development. We learned and we were expert enough to overcome the challenges we faces with our knowledge and experience.

3.03. Ensure that specifications for software on which they work have been well documented, satisfy the users’ requirements and have the appropriate approvals.

This was the most exhausting this to do when we were developing our project. But we were able to develop in a correct way since we were documenting everything according to the standards right from the start. Since we were the clients we were satisfied and also the panel was satisfied about our scope and the requirement gathering revealed some of the key factors to be added into our app.

We made sure that all what we did was according to the professional manner. We realized at the end how much documentation was important from right from the start. We used git-hub as a VCS to show and keep track of our project

3.04. Ensure realistic quantitative estimates of cost, scheduling, personnel, quality and outcomes on any project on which they work or propose to work and provide an uncertainty assessment of these estimates.

We scheduled work and personnel regarding our individual strengths and weaknesses as mentioned above. We had scheduling time slots for work since we had many other projects to do. Our time frames should be real and achievable.   

3.15. Ensure adequate testing, debugging, and review of software and related documents on which they work.

We were following the waterfall model so that we did all testing, debugging, and all the other development processes throughout the working project. We had some presentations all thorough the developing phase and we added and discarded some of the things in our project. 

We had a lot of positive feed-backs to our app so then we knew that we were doing the right way. At some times our server crashed and we had to re build it stronger.