Problems in Software Development - Case Study Example

Any software before it is put into use should be thoroughly tested to check for any bugs that exist within the software. Testing should be done both in black boxes testing to see if the software outputs the correct result after being fed with any data. Then white box testing should be done to see if the software structures and codes have any dead code. This will eliminate a situation where the software is having may be a lot of loops but some of them are not functional. The white box testing will also see that each loop is working correctly against its specification.

This will allow for changes to be made in the software even if it has passed a certain software development life cycle. This is made possible by developers interacting with the users of the software at each stage of development so that they can make suggestions of any changes that they would like made to the software or improvements. This will lead to the deployment of software that is accepted and also meets the user's needs.

The activity diagram shows the different process followed before the registration of a member to a certain training program is successful. First, the user has to submit the application form with all his or her details such as name, contact information, and id number. Then the administration verifies the application if the user has made any anomaly and if everything is okay the administrator checks for the existence of the space in the applied training program. If there is no existence of space the application is rejected and if the space exists the application is processed and so the client is billed for membership. All the activities end by having some feedback to the client on the status of the application if it has been accepted or rejected.

The conceptual diagram shows the relationship between the different entities in the system and the attributes they hold. The member entity has the attributes id which is a primary key, name, address, email, and telephone. There are many to many relationships between the member and the training program signifying that a member can enroll in more than one training program and one training program can have more than one member enrolled in it. This leads to needing of breaking off that relationship with a new attribute allocate program. The training program has an attributed the training code which is a primary key and the title. Due to the many-to-many relationship between the training program and the trainer, there was a need to break this relationship by adding a new entity allocate trainer which holds the primary key training code and trainer id as its foreign keys. There was a one-to-many relationship between the rooms and the training program meaning that a room can be allocated to more than one training program but a training program cannot be allocated more than one room.

The class diagram signifies the different classes that will exist in the making of the system which are the person class, member class, trainer class, training program, and room class. Due to the existence of attributes that are similar between the trainer class and the member class, there was a need to create a superclass person where the common attributes are declared. The member and trainer class will now inherit those attributes from the superclass eliminating the repetition of attributes in all classes. The room class has the methods that will be used to set the room code, capacity, type, and capacity. This class also holds the access methods for the different attributes which are methods declared as the get methods. There is a relationship between the room and the training programs where a program is supposed to be allocated to the different rooms. There is also a relationship between the trainer and the programs where a trainer is allocated a certain program. The members also hold a relationship between them and the different programs they enroll in. Every class diagram has the top part holding the name of the class and the middle part holding the attributes that are within the class and the bottom part holding the different operations carried out within the class.