Posted: December 16th, 2022

ISY302 – IS Project 1

ISY302 – IS Project 1 (Sem 2, 2019)

IS Project 1 is the first of the two capstone units in your course. So, you are required to work on a real-world project from a client. Your real-world project should contain details of your client’s requirements. A detailed description of your real-world project specifications should be made available to your lecturer by the start of week 2. The complexity of any real-world project should at least be equal to the complexity of the CCSAS project discussed below in this document.

Note that the CCSAS is only provided as an example you will be required to source your own project specification from a real-world client. This document focuses on the deliverables of the project.

Specifically, you should read Section 2.3.1 to learn about System Requirement Specification documentation & Project Management Plan documentation. In addition, Section 2.3.2 addresses the expected deliverables of this project from Software Design Document perspective. This semester the project focus is on the analysis and design of your system. In the next semester you will have another project management plan to mainly implement, deploy and test the system.

Course Co-ordinator’s Student Advising System (CCSAS)

Course Co-ordinators (CCs) are academics with additional responsibilities of managing student queries regarding a course. Their main responsibilities are advising new and current students about the correct subjects to register in a given study period, deciding credit grants (also known as recognition of prior learning) and deciding course completions. These responsibilities require knowledge of the status of the subjects being completed or yet to be completed vis-a-vis the stipulated subjects in the program map for the course. Hence this is a knowledge management activity. An IT tool called CCSAS is required to help CCs in this knowledge management activity

1. Business Requirements:
The CCs requirements can be broadly classified into four categories:

a) Creation of Program Maps for a course.

b) Support during registration (enrolling) advice session.

c) Student during Credit Grants (CG) advice session.

d) Support while deciding Course Completions.

1.1 Creation of Program Map (PM)

Each course follows a pre-defined course structure indicating the subjects in the course and an ideal schedule in which a set of subjects should be studied in a study period. In addition, it contains other details such as the credit points for each subject as well as any pre-requisites and co-requisites for each subject. Hence the CCSAS should allow the CC to create one for the course. Once the PM is

ISY302 – IS PROJECT 1 DETAILS, T2 2019

1 | P a g e

created the system should create a copy of the PM for each new student in the course with a status of “not enrolled” for each subject in the map.

1.2 Support during registration (enrolling) advice session

A student may seek CC advice regarding selection of subjects while enrolling a given study period. The

CC requires a Program Map (PM) of the course along with knowledge of the subjects completed and yet to complete subjects, while advising the student. The PM contains a map of the required subjects to be completed for the course during each study period. Hence the CCSAS should recommend the subjects to be enrolled when the CC enters the student’s details (say student id) in the system.

Moreover, when the student enrols in a subject, the CCSAS should either automatically update the subjects enrolled or allow the CC to add an entry for each subject that been enrolled. Note that automatic update would require integration with any existing subject registration system. In addition, the system should also change the status of the subject either automatically or manually to reflect whether the student has “not enrolled” or “enrolled” or “un-enrolled” or “completed”, (passed) or “not completed” the subject (failed) or whether it has been deferred. The system should also allow update of details such as the study period (e.g. semester 2, year 2019), grade obtained, institution details etc, every time a student registers for a subject. This means, for every attempt of the subject, the system should keep a track of the details. Since the CC refers to the PM while advising the student, each student should have a customised copy of the program map. The status update of each subject should be made in the custom copy of the PM. The report of the status of each student should be presented on the program map with colour codes to represent the status.

1.3 Student during Credit Grants (CG) advice session

A CG is an exemption from studying a subject in recognition of prior learning or learning at an external institution (cross-institutional study). The CC should be able to enter details as the study period (e.g. semester 2, year 2019), grade obtained, institution details etc, every time a student gets a CG for a subject. The CC should also be able to change the status of the subject as detailed in the previous section.

1.4 Support while deciding Course Completions

A Course Completion signifies that a student has completed all the learning requirements of the course and would not need to study any more subjects. The CC should be able to get a report from CCSAS indicating whether a student has completed all the learning requirements of the course.

2. Project Management Requirements:

This semester you will focus on analysis and design of your project and in the next semester you will implement the system as a web application. You will be required to work individually. Each student

ISY302 – IS PROJECT 1 DETAILS, T2 2019

2 | P a g e

should complete their own project. You should also use Scrum framework (except for the implementation part) for project management and GitHub Distributed Version Control as a tool. The Scrum milestones (deliverables) expected in this project are:

(a) Project Management Plan (PMP) and Software Requirement Specification (SRS) report

(b) Software Design Document (SDD)

2.1 Scrum Framework

Scrum is an agile project management framework to manage who does what and when (see Figure 1). It principally involves a Product Owner, who creates a list of Product Backlog Items (PBI) where each PBI is a sub-part of the project. Each PBI is taken in a Sprint session, typically 2 to 3 weeks to solve (see Figure 2).

Please refer to

https://www.collab.net/sites/default/files/uploads/CollabNet_scrumreferencecard.pdf for a cheat sheet on Scrum and to watch videos at https://www.collab.net/services/training/agile_e-learning for finer details such as:

Intro to Scrum (17 min)
Backlog Refinement Meeting (13 min)
Sprint Planning Meeting (10 min)
Daily Scrum Meeting (9 min)
Sprint Review Meeting (13 min)

Sprint Retrospective Meeting (15 min)

Figure 1: What is a scrum

(Ref: https://www.bing.com/videos/search?q=what+is+scrum+agile&view=detail&mid=D4887D01F699C315B56FD4887D01F699C315B56F&FORM=VIRE)

ISY302 – IS PROJECT 1 DETAILS, T2 2019

3 | P a g e

Figure 2: Overview of scrum framework

(Ref: https://www.bing.com/videos/search?q=what+is+scrum+agile&view=detail&mid=D4887D01F699C315B56FD4887D01F699C315B56F&FORM=VIRE)

2.2 Git + GitHub

Ref: https://geo-python.github.io/2017/lessons/L1/course-environment-components.html

Git is a version control software (developed by a rather famous Finn named Linus Torvalds – he also created Linux!) that is used to track and store changes in your files (often source code for programs) without losing the history of past changes. Files in Git are stored in a repository, which you can simply think of as a directory containing files (or other directories) related to a single ‘project’. Git is widely used by professionals to keep track of what they’ve done and to collaborate with other people.

GitHub is a web-based Git repository hosting service and social network. It is the largest online storage space of collaborative works that exists in the world. It is a place where you can share your code openly to the entire world or alternatively only to your collaborators working on the same project. GitHub provides a nice web-interface to your files that is easy to use. It is a wonderful way for exploring the codes and documentation or e.g., teaching materials such as those in our course.

Both Git and GitHub provide many more features than the ones mentioned here, but for now we are happy to understand the basic idea of what they are.

For information on GitHub and Distributed Version Control, go to:

https://geo-python.github.io/2017/lessons/L2/intro-to-GitHub.html

2.3 Scrum Milestone Requirements

A milestone is an output produced following a major accomplishment of a project. Each student is required to produce two documents, namely (a) PMP & SRS report in Assessment 1 (b) SDD in

Assessment 2. The details of these documents are discussed in the following two sub-sections. You may use GitHub to manage the daily Scrum activities for the two documents.

ISY302 – IS PROJECT 1 DETAILS, T2 2019

4 | P a g e

2.3.1 Project Management Plan (PMP) and Software Requirement Specification (SRS) report requirements (see unit outline for weighting of marks and due dates for this activity)

A PMP is used to manage and monitor the project plan, thus providing clear guidelines for the project. You may use the template provided in Section 2.4 while writing the PMP & SRS but restrict the content to expectations specified here:

Table of Contents

1. Introduction
1.1 Project Overview
1.2 Project Deliverables: SPMP, SRS in A1 and SDD in A2.
1.3 Reference Materials
1.4 Definitions and Acronyms

2. Project Organization

2.1 Process Model: Agile
2.1.1 Project Planning

2.1.2 Requirements Analysis: Use SCRUM features such as Product Backlog Items written in User Story form, Sprint Tasks (this section should be in detail as it is the SRS. Each item and sub item must

be indexed so that it can be referenced again in Assignment 2 Software Design Documentation) 2.1.3 Software Design: Architecture of web application, GUI design, process & workflow design,

database design (mention this will be delivered as a milestone in the 2nd assessment, so do not provide in-depth details here)
2.1.4 Analysis Review

2.1.5 Client Project Review
2.1.6 Prototype: Front end prototype
2.1.7 Client Presentation
2.2 Organizational Structure
2.2.1 Project manager and Tasks
2.3 Organizational Boundaries and Interfaces
2.3.1 GitHub Communication
2.3.2 Meeting Times
2.4 Project Responsibilities
2.4.1 Project Management
2.4.2 Project Sponsor (in case of real-world projects)
2.4.3 Liaison manager (in case of real-world projects)

2.4.4 Document Editor
3. Managerial Process
3.1 Management Objectives and Priorities
3.2 Assumptions, Dependencies and Constraints
3.2.1 Assumptions
3.2.2 Dependencies
3.2.3 Constraints

3.3 Risk Management: Details of individual team risk management assessments should be provided
3.3.1 Analysts perspective

3.3.2 Design perspective: Front end, process, database
3.3.3 Project Management perspective
3.4 Monitoring and Controlling Mechanisms

4. Technical Process
4.1 Methods, Tools and Techniques
4.2 Software Documentation
4.3 Project Support Functions

ISY302 – IS PROJECT 1 DETAILS, T2 2019

5 | P a g e

4.4 Work Elements, Schedule (do not include Budget)
4.4.1 Overall Project Plan

2.3.2 Software Design Document (see unit outline for weighting of marks and due dates for this activity)

Assessment 2 of this unit requires you to write an SDD. This document should be at a detailed design level. This means, all the major components of the system should be designed with a satisfactory level of granularity such that if your SDD is given to a programmer to implement, it should be easily implementable. In addition, the design should match the requirements specified during the Requirement Analysis activity (see Section 2.1.2 Requirements Analysis in your A1 document). That is, each design component should be indexed and should be traceable to a requirement specification in Section 2.1.2. You may use a matrix to manage this. Specifically, designs are required for: business component identification, the front design end, process & workflow design, database design and security concerns in design. You should use the Model View Controller (MVC) framework for the server-side components of the process design.

The structure of the SDD should be as follows:

Table of Contents
1. Introduction
1.1 Definitions and Acronyms
2. SDD Organization

2.1 Business Component Design: Each Business Component has a specific business purpose should have the following dimensions
2.1.1 Business Purpose: Why does it exist?
2.1.2 Activities: What simple, cohesive activities are regularly performed?
2.1.3 Resources: What tangible assets and human resources are required?
2.1.4 Governance: How are activities and resources managed?

2.1.5 Business Services: What is taken form and offered to other components? (consider people, process and technology together)
2.2 Front End Design: Consider structural design of each web page using mock-ups

2.3 Process & Workflow Design: Consider drawing UML activity diagrams for each user story
2.4 Database Design: Provide the overall E-R diagram with explanation and rational
2.5 Security in Design: Consider using STRIDE principles for Application Security
3. Conclusion (Provide the traceability matrix here from requirements to design components)
4. References

The following five sub-sections discuss these components of the design in more detail.

2.3.2.1 Business Component Diagram

A business component diagram identifies the core business components in the architecture. You may draw these as modules and sub-modules required for managing the business. This activity will allow you to think of the business components required for the system without being concerned about the technical aspects of the system. The business component diagram can be drawn using an online diagramming tool such as LucidChart1.

2.3.2.2 Front End Design

1 https://www.lucidchart.com

ISY302 – IS PROJECT 1 DETAILS, T2 2019

6 | P a g e

Most modern business applications are web based. Hence the front end-design should be for web-based interfaces. So, you should consider front design from HTML structure perspective but not necessarily using HTML. In other words, you may use mock-up tools such as Balsamiq2 to design the front end. However, in the next semester you should use HTML, CSS, JavaScript and AngularJS during the implementation. CSS or Cascade Style Sheet is a styling language to manage the presentation of the HTML and the data. JavaScript is a browser-based script language for better user interaction and AngularJS is a JavaScript library for separation of concerns such as presentation, data and control on the client side.

Watch this video from Edureka for a quick introduction to HTML. https://www.youtube.com/watch?reload=9&v=bsMtNF3SMjo (1 h: 54 m)

Additionally, you should watch this video from Edureka for a quick introduction to CSS, JavaScript and AngularJS.

https://www.bing.com/videos/search?q=web+development+edureka+youtube&view=detail&mid=9 BCCF83B0A30FB85A4B99BCCF83B0A30FB85A4B9&FORM=VIRE

2.3.2.3 Process & Workflow Design

A process defines a sequence of steps to be completed to accomplish a task and a workflow is a sequence of processes to accomplish a business process. For example, a process in CCSAS could be to update the status of a subject studied by a student and this could be one among the many processes to be completed while managing the workflow for Course Completion. You should consider using the MVC framework in the front-end and in the backend while managing the workflow designs. You are required to use the business components identified in Section 2.3.2.1 as Models within the MVC framework.

Read the first five paragraphs from this link to get a quick introduction to MVC.

(https://www.tutorialspoint.com/mvc_framework/mvc_framework_introduction.htm).

In addition, read the following to learn the principles of MVC framework in front end designs.

https://developer.chrome.com/apps/app_frameworks.

You should use UML’s Activity Diagrams to draw the workflow design. Your Activity Diagrams should have MVC components wherever possible, both in the front end as well as in the backend. As before you may use LucidChart to draw the diagrams.

2 https://balsamiq.com/download/

ISY302 – IS PROJECT 1 DETAILS, T2 2019

7 | P a g e

2.3.2.4 Database Design

Database designs are required to ensure that the data is structured (organised) appropriately for easy maintenance and efficiency during runtime. You may use MS Access as a tool to design the E-R diagram of the system. This activity ensures that you are knowledgeable of database management principles.

2.3.2.5 Security in Design

Security is a grave concern in most modern web applications. You should design security components in your design. You may consider the Confidentiality Integrity Availability (CIA) principles for this. This (http://www.doc.ic.ac.uk/~ajs300/security/index.html) URL from a student from Imperial College, London provides an easy understanding this principle. Confidentiality can be maintained by using Authentication and Authorization as well as by using encryption. Integrity involves maintaining the consistency, accuracy, and trustworthiness of data over its entire life cycle. Access control matrix needs to be designed to manage this principle. You need to define who can access each resource and whether an actor has “read”, “write”, “execute” privileges to each data management resource used in the system. Availability refers to uptime of the system and how it could be maintained.

2.4 Templates for PMP & SRS

Use one of the following and edit appropriately:

http://www.utdallas.edu/~chung/RE/Presentations10F/Team-hope/5%20-%20Project%20Plan.pdf

http://teaching.csse.uwa.edu.au/units/CITS4401/practicals/James1_files/SPMP1.pdf

ISY302 – IS PROJECT 1 DETAILS, T2 2019

8 | P a g e
=======
– Sample Assignment Solution
Table of Contents
1. Introduction 2
1.1 Project Overview 2
1.2 Project Deliverables 2
1.3 Reference Materials 2
1.4 Definition and acronyms 2
2. Project Organization 2
2.1 Process Model 2
2.1.1 Project planning 2
2.1.2 Requirements Analysis 2
2.1.3 Software Design 3
4
2.1.4 Analysis review 4
2.1.5 Client Project Review 4
2.1.6 Client Presentation 4
2.2 Organization Structure 5
2.2.1 Project Manager and tasks 5
2.3 Organization boundaries and interfaces 5
2.3.1 GitHub communication 5
2.3.2 Meeting times 6
2.4 Project Responsibilities 6
2.4.1 Project management 6
2.4.2 Project sensor 6
2.4.3 Liaison Manager 6
2.4.4 Document Editor 6
3. Managerial Process 6
3.1 Management Objectives and priorities 6
3.2 Assumptions, Objectives and Priorities 7
3.2.1 Assumptions 7
3.2.3 Dependencies 7
3.2.4 Constraints 7
3.3 Risk Management 7
3.3.1 Analysts perspective 7
3.3.2 Design perspective: Front end, process, database 8
3.3.3 Project Management perspective 8
3.4 Monitoring and controlling mechanisms 8
4. Technical Process 8
4.1 Methods, Tools and Techniques 8
4.2 Software Documentation 8
4.3 Project Support Functions 8
4.4 Work Elements, Schedule (do not include Budget) 9
4.4.1 Overall Project Plan 10
References 11

1. Introduction
1.1 Project Overview
this section provides the overview of the project. That what the project is. This document shows the requirements and the specifications of the ETA (Estimated time of arrival) direct platform. This platform is used to track the employees work and their responsibilities. It shows their work in the form of a profile generated for them that shows the orders provided by the company as complete, incomplete or pending etc.
1.2 Project Deliverables
The project deliverables include;
 Software Project Management Plan (SPMP)
 Software Requirements Specification (SRS)
 Software Design Document
1.3 Reference Materials
The reference material of the document are the websites of “Service Steam Limited” and the “ETA direct officials”.
1.4 Definition and acronyms
• ETA: Estimated time of arrival
• SRS: Software Requirements Specification
• SPMP: Software Project Management Plan
• NBN: National Broadband Network
2. Project Organization
2.1 Process Model
Agile process model shows the incremental development. It performs the activities step by step.
2.1.1 Project planning
Project planning shows the plan of the project. It shows the follow of activities. In our project;
• The employee registers or login to the ETA direct.
• Managers provide trainings to the employees.
• An employee profile is made.
• Employees activate the work route on their ETA profile.
• The work orders are marked as completed, closed, unscheduled or pending.
• The managers evaluate employees work based on their profiles.

2.1.2 Requirements Analysis
Following are the requirements that the Service stream wants ETA to do for him.
2.1.2.1 As a user, the employees and the managers should be authenticated.
2.1.2.2 They should be trained well about how to use the ETA direct platform.
2.1.2.3 As a worker, they should have a profile which shows their status.
2.1.2.4 When the employees start their work on the day, they should activate their work route and then keep updating it.
2.1.2.5 The orders should be displayed with their status as completed, starred, closed, unscheduled or pending.
2.1.2.6 The employees should change the status of orders when they complete it. They should also provide the proof of order completion.
2.1.2.7 Once the order is completed, the managers should evaluate it and update the employees profile ranking.
2.1.2.8 When the workday ends, the users should deactivate their work profile showing that they are not on work now.
2.1.3 Software Design
This section shows the different designs of the software being made. It shows the basic flows of the software and shows how it will look like.

2.1.4 Analysis review
The ETA basically has the following requirements;
• User registers or logs in to the system.
• Mangers provide training to the user.
• When user starts work, he activates the work route.
• The orders have the status as completed, starred, closed, unscheduled or pending.
• Employee changes the order status after completing.
• Then the manager evaluates order.
2.1.5 Client Project Review
This show that how the client sees the project is. This section shows the client expectations. In case of ETA, the client project review is
• The client wants that he should be provided the fast service.
• He should be provided with the best facility and work.
2.1.6 Client Presentation
The client of the system, that is Service Stream Limited in this case, must present his expectations and the requirements. Here, the client wants;
• Employees should be able to login.
• Employees should be able to activate their work route.
• Managers can track and instruct the employees.
• The platform should be user friendly, easy to use and reliable.
2.2 Organization Structure
The ETA contains three layers of structure. The first layer is of the Field Supervisors of the organization, second is of the managers and the third one is of the employees.

2.2.1 Project Manager and tasks
Project manager manages the project and its workers. In our current project, the project manager provides training to the employees and then assigns orders to them and then manages them.
2.3 Organization boundaries and interfaces
We can find out the organization boundaries and interfaces by GitHub communication and meeting times.
2.3.1 GitHub communication
Repository is the basic element of the GitHub communications. The total communication includes the whole organization, repository and the working teams.
• The organization contains the managers, field supervisors and the working employees.
• Repository contains all the files of the project that are documented and then stored in the repository.
• Working team includes all the employees of the organization. The basic element of the working team is an employee. It also contains the client and the other stakeholders of the project under discussion.
2.3.2 Meeting times
Meeting times means the meeting that are held to find out and set the organization boundaries and the interfaces. Meeting times basically show the boundaries or limits. So, they are used to find out the organization boundaries and the interfaces.
The interfaces used in this project are the mobile phone, computers and the cloud database or the internet.
2.4 Project Responsibilities
2.4.1 Project management
Project management is the initiation, planning, executing, managing and closing the work done by the management team. Project manager is responsible of the project management. Project management is done to avoid any failures in the system.
2.4.2 Project sensor
Project sponsor means the stakeholders or the clients responsible for providing the resources for the project. We must work according to their expectations. In our present project, Service Stream limited is the project sponsor, that is a network services providing company. They want the project to manage their work.
2.4.3 Liaison Manager
Liaison manager is responsible for the communications between the managers and the other people. In our present case, the liaison manger is responsible for communications between the managers of the project, project stakeholders and the project sponsors. He is responsible for it if there are any communication hindrance between the managers and the other people.
2.4.4 Document Editor
Document editor is responsible for the edition of all the documents of the project. If there is any contract between the stakeholders and the managers or any requirement change occurs, then the document editor is responsible for all these changes.
3. Managerial Process
3.1 Management Objectives and priorities
Management objectives shows the expectations of the management and their priorities show that what they want the project to perform.
• In Service Stream limited, the management wants to track the employees works and their efficiency. They want to track that how fast and in what effective way, the employees perform the work. So, they want to make an automatic system for employees work and efficiency evaluation, in the form of ETA.
• Management priorities show that what they want in comparable way. What is their priority. Either they want the work to be efficient or fast or the both.

3.2 Assumptions, Objectives and Priorities
3.2.1 Assumptions
Service Stream has the following assumption that must be included in ETA;
• There is a fixed communication between the organization and the customers that should keep on going. For this purpose, fixed line communication networks are maintained between the company and the customers.
• The basic cash flow assumption for the remote segment of Network Construction is that Service Stream proceeds to attempt huge work for or for the benefit of the real portable media transmission bearers in Australia. This expect existing contracts are expanded, new contracts are granted, and edges stay stable. No incomes have been included for NBN plan and development exercises past the current MIMA and DCMA programs.
3.2.3 Dependencies
There are the following dependencies in the Service Stream organization;
• All the employees depend on the field supervisor. They must gain or follow the instructions of the field supervisors.
• The activation of the working route depends upon the availability of the orders in the customers profile or to the organization.
3.2.4 Constraints
The constraints that are important in a project are;
• Time
• Cost
• Scope
Time constraint shows that how much time is available for the development of the project. So, the workers work according to the time available. Cost constraint shows the available cost and scope basically defines the system boundaries. All these have a relationship between them, and they are managed according to that. The scope constraint of the system shows that it is used only by the company employees and the managers. No one else uses it.
3.3 Risk Management
3.3.1 Analysts perspective
According to the analysts, following risks should be managed.
• Strong internet should be used so that the work updates should not be late. Otherwise, these effects the efficiency of the work.
• One work assigned to more than one employee.
• Employee completed the work, but the customer is not available to confirm it.

3.3.2 Design perspective: Front end, process, database
3.3.3 Project Management perspective
Project should be managed efficiently. Else it can create risks. The risk that may occur are;
• The project may not be completed in the given time. This factor should be kept in mind and a project management plan should be followed so that the work is done on time.
• Project cost may increase than the expected cost. This may occur when the project has not been completed in the given time or when some extra features have been added to the project. It should also be managed from the start. So, that no problems occur at the end.
• If the project must be completed in short time, then its scope can be affected. So, scope should also be considered while completing the project so that all the functions are available in the project.
3.4 Monitoring and controlling mechanisms
Monitoring and controlling mechanisms are also used to show that the project being developed in within the given scope and budget constraints and will be completed on time. It includes the tracking, reviewing, evolving and reporting of the project. Its output are status reports, risk registers etc. This process basically shows the project progress at any time during the project development.
4. Technical Process
4.1 Methods, Tools and Techniques
Following are the method, tools and techniques being used in the project under development.
• Agile or iterative development method is being used in this project.
• The tools being used are the MS word, MS Visio, Visual studio.
4.2 Software Documentation
The software is documented using the APA style formatting. The documentations include;
• Software requirements specification document (SRS)
• Software Project Management Plan (SPMP)
• Software Design Document (SDD)
4.3 Project Support Functions
Project support functions means the functions that provide support to the project. These functions include;
• Collecting the project data. We collect the necessary data for project so that it is obvious to the developers of the project that what they must do.
• Compiling the project data. We compile the raw data in usable forms. These forms may be SRS, SPMP or something else.
• Configuration management control. It contains the functions to manage consistency in the different works that we must do for the project.
4.4 Work Elements, Schedule (do not include Budget)
Work elements show the basics or flow of the work. We work on these elements to complete the project. The main tasks of the project are;
• Introduction shows the basic introduction of the project and the introductory tasks.
• Project organization shows that which organization has requested the project and what are his expectations.
• Managerial process shows the managerial tasks of the project.
• Technical process shows that which processes and resources are being used.
The work elements of the project are

4.4.1 Overall Project Plan
The overall project plan shows the plan that how the project will go on. What steps will be performed at what time and what is the cost and what resources are used.

References
ETAdirect Overview. (n.d.). Retrieved from https://www3.technologyevaluation.com/research/solution/etadirect.html
What Service Stream Does. (n.d.). Retrieved from https://www.servicestream.com.au/services#service
ETAdirect Professional. (n.d.). Retrieved from https://www.fieldtechnologiesonline.com/doc/etadirect-professional-0001

Check Price Discount

Study Notes, Research Topics & Assignment Examples: Aquifer assignment »Tracing the historical justification for the evolution of the multiple use management approach as a response to the UN Convention on the Law of the Seas (UNCLOS)