Clone this repository and bring the code pieces you need into your BDSA Assignments GitHub repository.
In a new class library implement a class Student with the following properties:
- Id :
int - GivenName :
string - Surname :
string - Status :
Status(enum:New,Active,Dropout,Graduated) - StartDate :
DateTime - EndDate :
DateTime - GraduationDate :
DateTime
And the following rules:
- Status is only readable - figure out the business rules given the three dates compared to
DateTime.Now. - Id can only be set when the class is created
- Implement a nice
ToString()method
Note: Remember to do this Test-Driven - so create an xunit test library and implement the required tests there.
(cf. C#9N chapter 4 section Records)
Implement a new record ImmutableStudent with the same rules as above, only now all properties must be immutable like this:
public string Property { get; init; }Write a couple of tests where you test the built-in equality comparer and to string properties of a record.
Ensure that your new C# projects are attached to your solution and all tests are running in your GitHub action for PR.
Consider the three different constructs in C#:
- Class
- Struct
- Record
Explain some of the key differences between the three and give examples of where you would use each of them.
Write your answers in the final .pdf file.
What is the difference between a scenario and a use case? When do you use each construct?
Draw a use case diagram for a ticket distributor for a train system. The system includes two actors: a traveler, who purchases different types of tickets, and a central computer system, which maintains a reference database for the tariff. Use cases should include: BuyOneWayTicket, BuyWeeklyCard, BuyMonthlyCard, UpdateTariff. Also include the following exceptional cases: Time-Out (i.e., traveler took too long to insert the right amount), TransactionAborted (i.e., traveler selected the cancel button without completing the transaction), DistributorOutOfChange, and DistributorOutOfPaper.
Draw a sequence diagram for the warehouseOnFire scenario of Figure 2-21. Include the objects bob, alice, john, FRIEND, and instances of other classes you may need. Draw only the first five message sends.
This year, the Analysis, Design, and Software Architecture course has re-introduced the group project and the entire process for accessing the exam with regards to the mandatory activities has changed. You have been tasked with drawing a UML diagram to depict the new process. Looking at the slides from the first lecture, you have found all the information you needed to complete the task. Diligently, you have summarized all of them in the below bullet point list:
- After a student enrolls in the course, four mandatory activities (MA) require completion before being allowed to take the exam:
- MA1 requires a student to participate to an exam simulation;
- MA2 requires a student to submit and get approved 5 weekly;
- MA3 requires a student to participarte to three project reviews;
- MA4 requires a student to participarte to the project demo.
- Participation to MA1 needs to be confirmed by the teaching team.
- Each weekly activity submission needs to be verified by the teaching team.
- Participation to MA3 needs to be confirmed by the teaching team.
- Participation to MA4 needs to be confirmed by the teaching team.
Note: for the purpose of this task you must assume the following:
- The re-execution of mandatory activities must not be modelled. For instance, failing to participate to the exam simulation would require a student to take the second run of such activity. You must not model this detail.
- The number of Weekly activities can be arbitrary.
- Responsibility for the execution of activities must be modelled.
- No time constrain must be included, hence, a student could spent a lifetime completing the mandatory activities and project reviews before being accepted to the exam.
Using the solution for Exercise 4 and making use of event-based action (see below), include the process that describes:
- the teaching team sending the exam results to study administration (SAP);
- SAP registering the exams in the system;
- the students verifying their exam grade.
Event-based actions enable objects and signals to be transmitted to receiver objects. They allow you to distinguish between different types of events. You can use an accept event action to model an action that waits for the occurrence of a specific event. The notation element for an accept event action is a "concave pentagon"---a rectangle with a tip that points inwards from the left. If the event is a time-based event, you can use an accept time event action, whereby in this case, the notation is an hourglass.
To send signals, you can use send signal actions. Send signal actions are denoted with a "convex pentagon"---a rectangle with a tip that protrudes to the right.
[1] Seidl, Martina, Marion Scholz, Christian Huemer, and Gerti Kappel. UML@ classroom: An introduction to object-oriented modeling. Springer, 2015.
Draw a class diagram that models the following specifications:
- Each project has a name, a start date, and an end date.
- Each project is associated to a project manager, a name, a telephone, and a team.
- The project manager manages (by starting and terminating) a project and leads the team associated with the project.
- The project receives as input the requirements and produces a system. Both requirements and the system have a completion percentage and a description.
- Each team is composed by developers.
Draw a state machine diagram that models your GitHub action configuration; include all triggers that you have defined.
To submit the assignment you need to create a .pdf document using LaTeX containing the answers to the questions and a link to a public repository containing solution attempt.
Members of the triplets should submit the same PDF file to pass the assignments. Make sure all group names and ID are clearly marked on the front page. If in doubt about the name of the file, feel free to use the following standard: <Assignement#>-<Group#>-.pdf (e.g., as01-g01-emic-pate-rnei.pdf).