MITS5502
Developing Enterprise Systems
Research Case Study Project
50% deduction for Late Submission within one week
0 mark for Late Submission more than one week
0 mark for duplicated Submission or Shared Work
You will be marked based on your submitted zipped file on Moodle. You are
most welcome to check your file with your lab tutor before your submission.
No excuse will be accepted due to file co
uption, absence from lecture or lab
classes where details of lab requirements may be given.
Please make sure that you attend Lecture EVERY WEEK as low
attendance may result in academic penalty or failure of this unit.
MITS5502 Case Study Project
Copyright © XXXXXXXXXXVIT, All Rights Reserved. 2
Objective(s)
This assessment item relates to the unit learning outcomes as in the unit descriptors. It is worth
10% of the total marks for the unit.
Task
You are to explore an industry-tailored software solutions company named Lawson. Your case
study report should include FIVE software solutions that Lawson offer to their customers. Write
a description of each software solution.
Go to product index (https:
www.infor.com/solutions/all-products/) to find any FIVE software
solutions that you would to explore.
The report should be between 1,000 to 1,500 words.
Lawson company website: https:
www.infor.com
What to Submit
Your case study report using the template given on Moodle.
https:
www.infor.com/solutions/all-products
https:
www.infor.com
Software Requirements Specification (SRS) Template
MITS5502
(Research/CaseStudy Title)
(Student Full Name)
(Student ID)
Date: (mm/dd/yyyy)
Page 9 of 29
Table of Contents
1. Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms, and A
eviations. 4
1.4 Overview 4
2. The Overall Description 4
2.1 Product Perspective 4
2.1.1 System Interfaces 4
2.1.2 Interfaces 4
2.1.3 Hardware Interfaces 4
2.1.4 Software Interfaces 4
2.1.5 Communications Interfaces 4
2.1.6 Memory Constraints 4
2.1.7 Operations 4
2.1.8 Site Adaptation Requirements 5
2.2 Product Functions 5
2.3 User Characteristics 5
2.4 Constraints 5
2.5 Assumptions and Dependencies 5
2.6 Apportioning of Requirements. 5
3. Specific Requirements 5
3.1 External Interfaces 5
3.2 Functions 5
3.3 Performance Requirements 5
3.4 Logical Database Requirements 5
3.5 Design Constraints 5
3.5.1 Standards Compliance 5
3.6 Software System Attributes 5
3.6.1 Reliability 6
3.6.2 Availability 6
3.6.3 Security 6
3.6.4 Maintainability 6
3.6.5 Portability 6
3.7 Organizing the Specific Requirements 6
3.7.1 System Mode 6
3.7.2 User Class 6
3.7.3 Objects 6
3.7.4 Feature 6
3.7.5 Stimulus 6
3. 7.6 Response 6
3.7.7 Functional Hierarchy 6
3.8 Additional Comments 6
4. Change Management Process 7
5. Document Approvals 7
6. Conclusion 7
References 8
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and A
eviations.
1.4 Overview
2. The Overall Description
2.1 Product Perspective
2.1.1 System Interfaces
2.1.2 Interfaces
2.1.3 Hardware Interfaces
2.1.4 Software Interfaces
2.1.5 Communications Interfaces
2.1.6 Memory Constraints
2.1.7 Operations
2.1.8 Site Adaptation Requirements
2.2 Product Functions
2.3 User Characteristics
2.4 Constraints
2.5 Assumptions and Dependencies
2.6 Apportioning of Requirements.
3. Specific Requirements
3.1 External Interfaces
3.2 Functions
3.3 Performance Requirements
.
3.4 Logical Database Requirements
.
3.5 Design Constraints
3.5.1 Standards Compliance
3.6 Software System Attributes
3.6.1 Reliability
3.6.2 Availability
3.6.3 Security
3.6.4 Maintainability
3.6.5 Portability
3.7 Organizing the Specific Requirements
3.7.1 System Mode
3.7.2 User Class
3.7.3 Objects
3.7.4 Feature
3.7.5 Stimulus
3. 7.6 Response
3.7.7 Functional Hierarchy
3.8 Additional Comments
4. Change Management Process
5. Document Approvals
.
6. Conclusion
References