Developing ICT solutions + Development Methodologies

Developing ICT solutions + Development Methodologies

1. Testing

   • Module/Unit Testing
     • Unit Testing is a level of software testing where individual units/ components of a software are tested. The purpose is to validate that each unit of the software performs as designed.
   • Acceptance Testing
     • Acceptance Testing is a level of the software testing where a system is tested for acceptability. The purpose of this test is to evaluate the system’s compliance with the business requirements and assess whether it is acceptable for delivery.
   • White Box Testing
     • White Box Testing (also known as Clear Box Testing, Open Box Testing, Glass Box Testing, Transparent Box Testing, Code-Based Testing or Structural Testing) is a software testing method in which the internal structure/ design/ implementation of the item being tested is known to the tester.
   • Black Box Testing
     • Black Box Testing, also known as Behavioral Testing, is a software testing method in which the internal structure/ design/ implementation of the item being tested is not known to the tester. These tests can be functional or non-functional, though usually functional.
   • Integration Testing
     • Integration Testing is a level of software testing where individual units are combined and tested as a group. The purpose of this level of testing is to expose faults in the interaction between integrated units. Test drivers and test stubs are used to assist in Integration Testing.
   • System Testing
     • System Testing is a level of the software testing where a complete and integrated software is tested. The purpose of this test is to evaluate the system’s compliance with the specified requirements.
   • Grey Box Testing
     • In Gray Box Testing, the internal structure is partially known. This involves having access to internal data structures and algorithms for purposes of designing the test cases, but testing at the user, or black-box level.

2. Development Methodologies

   • Agile Methodologies
     • Large emphasis on real-time communication, usually face-to-face, over written documents. Most agile teams are located in a bullpen and include all the people necessary to finish the software. Most agile methods attempt to minimize risk by developing software in short timeboxes, called iterations, which typically last one to four weeks
   • Linear Methodologies
     • Once a phase of development is completed, the development proceeds to the next phase and there is no turning back.
   • Iterative Methods
     • The iterative model is a particular implementation of a software development life cycle (SDLC) that focuses on an initial, simplified implementation, which then progressively gains more complexity and a broader feature set until the final system is complete.
   • Crystal Methodologies
     • Each team has a different set of talents and skills and therefore each team should use a process uniquely tailored to it. And it means that the process should be minimized - barely significant.

3. ·