Consider a basic repository account that allows adding and removing files. Suppose each file contains information...

Transcribed Image Text:

Consider a basic repository account that allows adding and removing files. Suppose each file contains information about a person's vaccination record for infectious diseases. (a) [20 points] Create a class for the repository account (call the class RepoAccount). Specify the necessary attributes and methods for this class. This class should have between four to six attributes. Similarly. This class should have between four to six methods. The data types are not restricted to being primitive. An instance of the RepoAccount may be accessed by some designated instance of another class that can read the stored records. At least one non- primitive data type must be used. Every non-primitive data type can have a UML class and need to be included in the answer. Note: this question is not asking for a class diagram. (b) [10 points] Provide descriptions for each of the attributes identified for the RepoAccount class in part (a). (c) [10 points] Provide one reason for the RepoAccount class to satisfy the modularity principle. Consider a basic repository account that allows adding and removing files. Suppose each file contains information about a person's vaccination record for infectious diseases. (a) [20 points] Create a class for the repository account (call the class RepoAccount). Specify the necessary attributes and methods for this class. This class should have between four to six attributes. Similarly. This class should have between four to six methods. The data types are not restricted to being primitive. An instance of the RepoAccount may be accessed by some designated instance of another class that can read the stored records. At least one non- primitive data type must be used. Every non-primitive data type can have a UML class and need to be included in the answer. Note: this question is not asking for a class diagram. (b) [10 points] Provide descriptions for each of the attributes identified for the RepoAccount class in part (a). (c) [10 points] Provide one reason for the RepoAccount class to satisfy the modularity principle.

Answer rating: 100% (QA)

The image contains a text outlining a threepart question related to objectoriented programming and the design of a class named RepoAccount The questio... View the full answer