University of South Australia 

School of ITMS 

INFS 1021: Systems Analysis (SA) A3 Assignment – 

Group Length: 2000 words,  Weighting: 25%,  Due Date: 11 pm Sunday 31st May

INSTRUCTIONS TO STUDENTS
This task is to be done in groups which must have been approved by your tutor. Assignments will be returned to you within two to three weeks of submission. Feedback on this assignment will be provided via a rubric which will be available on the course website. Please read the assessment summary and assessment details sections of your course outline booklet carefully for further information relating to assessment in this course.
SPECIFICATIONS 
This assignment will enable you to improve your skills as a systems analyst and carry out various activities in the systems analysis phase of the systems development life cycle. It requires you to investigate and document system requirements, identify and document use cases, carry out domain modelling and use case modelling.
The assignment should be created using the template provided on the course website.
Each group member is also required to fill out the “Declaration of Contribution” form which is available in the assignment template document. As stated in the form, if any contribution does not meet the assessment requirements, the course coordinator may adjust individual marks up or down, depending on the level of contribution made.
Marking Criteria 
The rubric that will be used when assessing your work will be available on the course website. The word limit will not be checked for this assessment. This task will assess completeness of the objectives listed below.
• Completeness, suitability and thoroughness of responses to the questions
• Technical correctness of the various models created;
• Adequate presentation and format;
• Use of the template provided;
• Correct spelling and grammar;
• Clarity of expression;
• Clearly labelled questions and answers;
2 Submission Instructions 
The assignment MUST be submitted via Learnonline through the course website or via MyUniSA. Please submit ONLY ONE assignment per group – nominate someone to submit the assignment on the group’s behalf. Include as part of your submission ONE .pdf document containing the responses to the questions relating to the given scenario. Individual submissions will NOT be considered or marked. Refer to your course outline for further information regarding extensions. Late submissions will not be accepted for this course unless an extension has been approved by the course coordinator (see section on extensions in your course outline for further details). Late submissions that have not been approved will receive a mark of zero.
***IMPORTANT INFORMATION***
It is up to each group to make sure that the submitted work does not contain any parts copied from another group in this or any previous year, from this or any similar course; or from a common source such as a textbook or website. The assignment must be your own collective work, and not contracted to a substitute person. If we are suspicious, we reserve the right to call you in and to test your understanding of what you have submitted in an oral examination. If plagiarism is detected it will be investigated and appropriate consequences will follow.
SCENARIO
A Medical Practice has tasked your team to develop the requirements for their medical practice management system. The system is to allow the practice to record patient appointments and allow doctors to capture the medical history of their patients. A patient’s primary doctor can access the details of their patients at any time. However if a patient temporarily sees a different doctor, that doctor can only access the patient’s medical records during the consultation. The system must record the times when doctors are available during business hours from Monday to Friday, 8 am to 9 pm, and Saturday and Sunday from 9 am to 4 pm. The system must be available with 98% certainty during these business hours. Response times for accessing a patient’s record, which can be a maximum of 100 megabytes, must not exceed 7 seconds. At times doctors will also be able to be rostered as a locum service in shifts from 6am to 2pm, 2 pm to 10pm or 10pm to 6am. A doctor may not be rostered on for more than 40 hours per week and if rostered as a locum shift may not take another shift without a 14 hour break. The medical practice has ten doctors. Only one doctor will be rostered on a locum shift at a time. During business hours two nurses must also be rostered on and again may not work more than 40 hours per week. A doctor consults with patients in their office and must be able to access the system from their office. The history of all updates is logged and the system is backed up daily. The system logs a person out after ten minutes without use. Doctors on the locum roster are to be provided with a tablet device with mobile phone and global positioning system connections. The application on the device is to contain an emergency call button that contacts police in the event of an emergency and transmits the address that the doctor is consulting at. The tablet device application is to be able to connect with the patient records stored at the main medical practice but only show the record of the patient that the doctor is consulting with at that time. Doctors consult with patients in either fifteen minute or 30 minute blocks. In addition to a patient’s medical history, a patient’s record must include their name, address, date of birth, emergency contacts, any current medications, a photograph of their face and key details such as hair colour, eye colour, height, weight and gender. Associated with a patient but stored separately is their financial records – bills incurred, outstanding and medical insurance details. The reception staff must be able to manage appointments in person or on the phone for new and existing patients. After an appointment, the reception staff must be able to call up the billing information for a patient based on what services a doctor has provided, accept cash or electronic payment and print out invoices for the patient or their parent, guardian or carer. Note that a patient without private medical insurance receives a Medicare rebate on their services and a patient with private medical insurance receives an additional rebate but there typically is some gap fee that remains to be paid. The business manager for the Practice must also be able to access the system for basic accounting activities, transferring the data into a standard accounting package for analysis. The business manager must be able to identify the total Medicare rebate as well as the Private Insurance company rebates and invoice accordingly. The business manager must also be able to identify the costs of the business associated with the time sheets that doctors complete each week. Doctors enter their time sheets via their office computer. Finally doctors must be able to access the Internet from their terminals and as well use the specialist Pharmacy application provided by AAA Pharmacy Pty Ltd. Each doctor must be able to print scripts for patients from their office or the surgery, the receptionists print invoices for patients and the business manager prints report information. It is imperative that patient privacy is strictly respected so there must be suitable security measures in place to ensure this. The Practice has one IT administrator that can perform general IT duties for the terminals and servers but must not be able to access patient records without an additional password entered by the most senior doctor of the practice. The system is expected to handle approximately 300 patients.
QUESTIONS 1. 
SYSTEM REQUIREMENTS
 a. Who are the stakeholders for the system? Provide your response using the grid format and/or template given in the previous assignment. For each stakeholder identified, list what aspects of the system are of particular interest to them. Express stakeholders’ interests using the following template: “As a , I want to so that .” 
b. To collect information on the functional requirements for the system, what are some techniques that might be used? Identify what information would need to be obtained through interviews. Who would you interview? Include ten sample interview questions you would ask to obtain the required information. Ensure you obtain sufficient information to define use cases and create models. c. What are the primary functional requirements for the system? Provide your response using the format specified in lectures and tutorials. d. Identify and describe non-functional requirements for the system. Provide your response using the format specified in lectures and tutorials.

2. USE CASES 
a. Identify all the actors who will be using the system. 
b. Prepare a table containing all use cases and a brief use case description (1-2 sentences) for each use case. 
c. Draw a use case diagram for the system representing the actors and use cases identified. 

3. DOMAIN MODELLING 
a. List the domain classes for the system and their attributes. 
b. Based on the domain classes identified, develop a domain model class diagram showing domain classes with attributes, primary keys, relationships, and multiplicity constraints. 
c. Associations are the naturally occurring relationships between classes. They apply in two directions and can be read separately each way. For example two classes called Customer and Order could have the following associations: 
• A Customer can place zero or more Orders. 
• An Order must be placed by exactly one Customer. List all of the associations (in both directions) between the classes for the domain model in part b using the format specified above. 
4. USE CASE MODELLING 
a. Write a fully developed use case description for the use case Book Appointment. Assume the patient is new and making the appointment in person at the Practice. 
b. Develop an activity diagram for the use case in part a. 
c. Prepare a system sequence diagram for the use case in part a. 
d. Based on the domain model and the list of use cases developed, do a CRUD analysis for each of the identified classes. Provide your response in the CRUD table format given in Figure 5-13 of the textbook, pg 147, which shows use cases down the left and domain classes across the top of the table. 
5 Important Notes: 
• Justify and document any decisions and assumptions made. 
• You must use the templates/layouts provided in the course notes and/or textbook for any answers, tables, models, diagrams or use case descriptions created. Diagrams must conform to the UML notation used in this course. 
• Diagrams may be produced using a UML case tool or hand-drawn provided that they are legible and well laid out. It is the group’s responsibility to ensure these are appropriately presented and incorporated into the document template. 
• DO NOT include the scenario or question text in the document template. Use the template document as is. Do not modify any headings and include your responses in the area indicated. 
• Post any questions in relation to the scenario or assignment on the SA A3 Assignment – Group Q&A Forum on the course website.

Test of Association Assignment

Name________________________________

This assignment is worth 100 points. Each problem/part is worth 5 points each.

Due Date: ThursdayMay 21, 2020 by 11:59p.m. EST.

You do not have to type your responses. If you wish to provide hand-written work and scan your document, that is fine. Upload your final document with complete responses to the ‘Test of Association Assignment’ in Canvas.

1.       Some students in the masters of analytics program at Harrisburg University claim they are really good at soccer. To see whether there is an association among students and faculty in terms of the goals they can score in a soccer game, the analytics faculty invited students and teaching assistants (Ph.D. students) to play in soccer matches.  Every player was allowed to play in only one match. Over many matches, we counted the number of players who scored goals.

a.       The soccer.txt file is attached to the ‘Test of Association Assignment’ in Canvas. Import this file into R. Copy and paste your code below that shows where you imported the data. Name the data frame that you create ‘soccer.’

library(readr)

soccer <- read_csv("kochu/soccer.txt")        

b.      When you examine the data frame you imported into R, you will notice that it is not in the appropriate format for performing a chi-square test. Using some of the R categorical functions that you have learned in the course, convert the soccer data frame that you imported in part a in to a table such that the Job variable is on the rows and the Score variable is on the columns. Name the table you create ‘soccer_t’. Copy and paste your code below that created the table.

soccer_t <- read.delim("soccer.txt")

Table create below

c.       Develop the appropriate null and alternative hypothesis for testing an association among these variables. State the null and alternative hypothesis in the context of this problem.

H₀: There is no relationship between occupation with the frequency of scoring in a soccer match.

H₁: There is a relationship between occupation with the frequency of scoring in a soccer match.

d.      Run the chi-square test in R using the assocstats() function. Copy and paste your code and the output below. What is the value of the chi-square test statistic? What is the p-value related to the chi-square test statistic?

tab<- table(job,freq)

summary(assocstats(tab))

Chi-square test statistic is 12

The p-value is 0.2851

e.      Compute the χ² test statistic that you obtained from the R output in part d.  You should show your computations. Show the computations of the expected counts. Provide a final table that includes the observed counts with the expected counts in parenthesis for each cell. The final table should have row and column margin totals and a grand total.

summary(chisq.test(tab))

f.        Does the test statistic you found by hand in part e match the χ² test statistic from the assocstats() output in part d? State Yes or No.

No

g.       Use the pchisq() function in R to find the p-value associated with the χ² test statistic. Copy and paste your code below.  Does the p-value you found with the pchisq() function match the p-value from the assocstats() output in part d? State Yes or No.

YES

1-pchisq(12, 10, ncp = 0, lower.tail = TRUE, log.p = FALSE)

P value is 0.2850565 to four decimal places is 0.2851 

hence it is similar to the p-value using assocstats ()

h.      Using the p-value for this test, do you reject or not reject the null hypothesis?

Accept the null hypothesis

i.        State a conclusion back in terms of the context of the problem.

The null hypothesis is accepted because the p-value is greater than 0.05.

Final Research

Write a brief research report (up to about 7 pages, not including title page, abstract, and references), based on an analysis of the data file. Choose a hypothesis, cite at least three references to justify your hypothesis, test your hypothesis with an analysis of the DATA540.SAV file, and then report and discuss the results. Your results should include both descriptive and inferential statistics. 
 

Use APA format, including an introduction, abstract, method, results, and discussion section. Please refer to the APA manual: American Psychological Association   (2010).   Publication manual of the American Psychological Association.   (6th ed.).   Washington, D.C.

Lab 4 - Mutability

Lecturer:
Report Title:
Submit to:
Deadline for submission:

Student Name:
Student Number:
Programme of Study:
Module:

Contents

Description. 2

Aims. 2

Method. 2

Results and Testing. 2

Conclusions. 2

References. 2

Appendices. 2

 

Description

An immutable project can be defined as a program that cannot be changed once a variable has been instantiated. The program contains attributes that makes it impossible to be changed once it has been created (Kjolstad, Dig, Acevedo, & Snir, 2010). The project contains protective measures that make it impossible to add or remove objects once it has been created. Immutable program contains different objects that work together to ensure that the program is not destroyed once it has been created. The project involves testing an existing class known as Planet.java to see whether it has attributes that makes it an immutable program. The test is conducted by reading the code and establishing objects that makes it immutable and also developing a test.java class to test the planet. Java. The test class should be able to use the existing methods in the class planet and establish whether or not the class is immutable.

Aims

       I.            To determine whether the program is immutable

    II.            Develop a strategy that can be used to define immutable objects

 III.            To study and understand the Date object

 IV.            To develop a driver class for the project

Method

The methodology used to analyze the program to determine whether it is immutable is conducted using NetBeans IDE.  

Determining whether the program is immutable

The code below shows the declaration of the code as public final class Planet; this is because no children classes should be created from the immutable class Planet.

public final class Planet

{

}

The fragment of code from the program below shows string name and Date discoveryDate objects. It is an immutable program because the constructor public Planet has parameters.  The parameterized constructor makes it impossible for the project to be changed after it has been created.

public Planet (String name, Date discoveryDate)

{

     this.name = name;

this.discoveryDate = new Date (discoveryDate.getTime ());

  }

The object string name is immutable because once it is created it cannot be changed anywhere in the program.

Both the variables name and discoveryDate have get methods have seen below for each one of them.

public String getName()

  {

    return name;

  }

The public String getName() return name as it is evident in the fragment of code above.

  public Date getDiscoveryDate()

  {

    return new Date(discoveryDate.getTime());

  }

The code above public Date getDiscoveryDate() returns new Date().

The program does not have setter methods to enable change of the variables in the program once it has been created.

The tester code below proves that the class is immutable

// Driver class

import java.util.*;

class Test

{

    public static void main(String args[])

    {

        Date date = new Date();

        Planet p;

        p = new Planet("Testing the Planet Class", date);

        System.out.println(p.getName());

        System.out.println(p.getDiscoveryDate());

 

       

    }

}

The tester code shows that the variables defined in the class planet cannot be changed and it has to be re-used. As it is evident on the code above the class Planet has to be called so as to be able to access the variables name and discoveryDate using the get methods available in class Planet.

Strategy to define immutable objects

The best strategy to define immutable objects is by first opening a program using different java IDE. Once the program has been opened reading and understanding the code is important in understanding the type of program and objects. The objects is plays a critical part in determining the immutable nature of a program. The program should have a constructor that has parameters, there should be a get method for all the variables in the program and finally the program should not have a set method for any of the variables.

Understanding the date variable

The date variable when it comes to immutable objects is complex. This is because the date belongs to data type Date. It is evident in our test class above as we can see in the code below:-

Date date = new Date();

The object date had to be initiated using the function new Date (). The double initiation of date object makes it complex to use. Date object is discouraged from use because it has major flows since it was developed. Such flows includes it lacks time zone, the world contains different time zones. The lack of time zones in the java.util.Date makes it lack necessary features that is important to the users of the systems developed using the object. It also lacks time format that is necessary in ensuring that users of the system understand the time being displayed (Nikolic, 2017). The weakness makes it harder because the software engineer has to design a time format for the program which is time consuming. It also lacks a calendar system. The calendar system has to be developed hence adding work to the individual or team using java util Date for the function of software development. This is not flexible because it rates years based on the year 1900 and it results in problems when using years prior to 1900 (Nikolic, 2017).

Results and Testing

The planet class displayed in Figure 1 is the programmed being tested if it is immutable. Based on the tests above and using the test class in Figure 2 it was confirmed that the planet class is immutable. The test class produced the output below:-

It displayed the string “Testing the Planet Class”, the string was defined with the string posted in the test class. The date displayed was the current time defined on the test class but it was displayed using the function getDiscoveryDate from the Planet class. The same applies to the string name that was from class Planet.

Conclusions

In conclusion, the aims of the study has been met, this because the program has been confirmed to be immutable, the object date has been studying and understood perfectly,  the test class for the main program was developed and finally the strategy to define an object based on immutable program developed. The project is immutable based on (Haack, Poll, Schafer, & Schubert, 2017) definition of an immutable program. The program does not have setter methods that can be used to change the program after it has been instantiated. The program only contains constructors and getter methods that cannot be used to change the program variables once they have been instantiated.

References

 

Haack, C., Poll, E., Schafer, J., & Schubert, A. (2017). Immutable Objects for a Java-like

Language. German research foundation, Retrieved from https://www.cs.ru.nl/E.Poll/papers/esop07.pdf .

Kjolstad, F. B., Dig, D., Acevedo, G., & Snir, M. (2010). Refactoring for Immutability.

Making Classes Immutable, Retrieved from https://core.ac.uk/download/pdf/4824892.pdf .

Nikolic, D. (2017). Still using java.util.Date? Don’t! Programming Hints, Retrieved from

 https://programminghints.com/2017/05/still-using-java-util-date-dont/ .

Appendices

Figure 1: Class Planet

Figure 2:Class Test

Lab 4 - Mutability

“Immutable objects are simple. They can only be in one state, which is carefully controlled by the constructor. One of the most difficult elements of program design is reasoning about the possible states of complex objects. Reasoning about the state of immutable objects, on the other hand, is trivial.

Immutable objects are also safer. Passing a mutable object to untrusted code, or otherwise publishing it where untrusted code could find it, is dangerous — the untrusted code might modify its state, or, worse, retain a reference to it and modify its state later from another thread. On the other hand, immutable objects cannot be subverted in this manner by malicious or buggy code, so they are safe to share and publish freely without the need to make defensive copies.” 

—Brian Goetz, Java Concurrency in Practice

Introduction

An immutable object is one whose externally visible state cannot change after it is instantiated. The String, Integer, and BigDecimal classes in the Java class library are examples of immutable objects -- they represent a single value that cannot change over the lifetime of the object.

Lab Instructions:

Consider the following code:

import java.util.Date;

public final class Planet {

  String name;

  privatefinalDate discoveryDate;

  public Planet (String name, Date discoveryDate) {

     this.name = name;

this.discoveryDate = new Date(discoveryDate.getTime());

  }

  public String getName() {

    return name;

  }

  public Date getDiscoveryDate() {

    return new Date(discoveryDate.getTime());

  }

}

1.      Is this program immutable? If you think it is not, what changes would need to be implemented and why? If you think it is, explain why? To explain you need to create a tester class to run the code and see if you can change any values.

2.      Did you notice anything about the Date object? The Date object is no longer used in the latest versions of Java. Research why this is so and how it relates to Mutable Code.

3.      Using what you have learned about Mutability. Detail a strategy that could be used for defining immutable objects.

Remember to write your conclusions on your work.

Submission and Grading Details

This lab will form part of your complete Lab book, which must be submitted at the end of the module. You must reference your work.  You should follow the layout of a typical lab book, and add extra headings as necessary. Sample layout below:

·         Lab3 Mutability

o   Description

o   Aims

o   Method  

o   Results

§  Section 1 What is Mutability and Immutability

§  Section 2 Immutable Code or Mutable Code?

§  Section 3 Deprecated Object ‘Date’

§  Section 4 A strategy for defining immutable objects

o   Conclusions

o   Appendix

o   References 

	Marks Available
Description	5
Aims	5
Method	5
Results/Testing/Evaluation	10
Is code Mutability or Not, explain	15
Deprecated Object ‘Date’	10
Outline a Strategy that could be used	10
Conclusion	40
TOTAL	100