Project Name
Specification
and Design
Cohort: D

Group: 1
Group
members:
ABC 123...

Question

Project Name>
  Specification
  and Design
  Cohort: D
  
  Group: 1
  Group
  members:
  ABC 123 (Team
  leader)
  XYZ 456

Document Acceptance and Release Notice

This document is authorised for release
once all signatures have been obtained.

PREPARED:

Date:

/

(for acceptance)

Project Manager, Student Group

ACCEPTED:

Date:

/

(for release)

Project Sponsor, VIT

Table of Contents

1. Executive Summary. 1

2. Specification. 1

2.1 System
Description. 1

2.2 Feasibility
Analysis. 1

2.2.1 Technical
Feasibility. 1

2.2.2 Economic
Feasibility. 1

2.2.3 Organizational
Feasibility. 1

2.3 Requirements
Specification. 1

2.3.1 Functional 1

2.3.2 Non-functional 1

2.4 Use
Cases. 1

2.4.1 Use
Case Diagrams. 2

2.4.2 Use
Case Descriptions. 2

2.5 Context
Model 2

3. Design. 2

3.1 Architectural
Design. 2

3.2 Hardware
Specifications. 2

3.3 Database
Structure. 2

3.4 Interface
Design. 2

3.5 Sequence
Diagrams. 2

3.6 State
Diagrams. 2

4. References. 3

List
of Figures

List
of Tables

Glossary

UI

User Interface

1.
Executive Summary

2.
Specification

Objectives

2.1
System Description

2.2
Feasibility Analysis

2.2.1
Technical Feasibility

2.2.2
Economic Feasibility

2.2.3
Organizational Feasibility

2.3
Requirements Specification

2.3.1
Functional

2.3.2
Non-functional

2.4
Use Cases

2.4.1
Use Case Diagrams

2.4.2
Use Case Descriptions

2.5
Context Model

3.
Design

Objectives

3.1
Architectural Design

3.2
Hardware Specifications

3.3
Database Structure

ER Diagram and/or Class Diagram

3.4
Interface Design

Wireframe diagrams, and any other interface requirements

3.5
Sequence Diagrams

Interaction Diagrams

3.6
State Diagrams

If applicable

4.
References

Marking Guide:

Criteria (used as a guide only)

Exceeds
  Expectations
  
  (100% -
  80%)

Meets
  Expectations
  
  (80% -70%)

Approaches
  Expectations
  
  (70% -
  50%)

Does Not Meet
  Expectations
  
  (50%- 0%)

Other
  Evaluation

Executive Summary

Document format

Connectedness between Sections

Completness

Specification

System Description

Feasibility Analysis

Requirements Specification

Use Cases

Context Model

Misc elements

Design

Architectural Design

Hardware Specifications

Database Structure

Interface Design

Sequence Diagrams

State Diagrams

Misc elements

Grammar

Spelling is
  satisfactory

Grammatical
  expression is satisfactory

Aditi · Accepted Answer

Specification and Design
Cohort: D
Group: 1
Group members:
ABC 123 (Team leader)
XYZ 456
Document Acceptance and Release Notice
This document is authorised for release once all signatures have been obtained.
PREPARED:	Date:	/	/
			
 PAGE 2
(for acceptance)

Project Manager, Student Group
ACCEPTED:	Date:	/	/
(for release)	Project Sponsor, VIT
Table of Contents
1. Executive Summary	1
2. Specification	1
2.1 System Description	1
2.2 Feasibility Analysis	2
2.2.1 Economic Feasibility	2
2.2.2 Organizational Feasibility	3
2.2.3 Technical Feasibility	3
2.3 Requirements Specification	4
2.3.1 Functional	4
2.3.2 Non-functional	4
2.4 Use Cases	4
2.4.1 Use Case Diagrams	4
2.4.2 Use Case Descriptions	5
2.5 Context Model	6
3. Design	6
3.1 Architectural Design	6
3.2 Hardware Specifications	7
3.3 Database Structure	8
3.4 Interface Design	9
3.5 Sequence Diagrams	11
3.6 State Diagrams	13
4. References	14
List of Figures
FIGURE 1: USE CASE DIAGRAM	5
FIGURE 2: CONTEXT MODEL OF CRM	6
FIGURE 3: ARCHITECTURAL DESIGN OF CRM	7
FIGURE 4: DATABASE STRUCTURE	8
FIGURE 5: INTERFACE DESIGN	11
FIGURE 6: SEQUENCE DIAGRAM OF CRM	12
FIGURE 7: STATE  DIAGRAM OF CRM	13
Glossary
UI	User Interface
1
1. Executive Summary
The goals and requirements of the "CRM for university" project are laid forth here. The specification, system description, feasibility study, use case, and context model are all provided thereafter. The same is true for the presentation of system design.
2. Specification
Specification aims to achieve the following goals:
The analysis and forecasting of expenses.
A workflow's methodology is defined by this.
Indicate the details that would be lost in a visual representation.
Information on the kind and amount of resources needed for software development is provided.
2.1 System Description
Customer Relationship Management (CRM) is software that helps businesses maintain positive relationships with their customers and manage how they communicate with them[1]. Using customer relationship management (CRM), colleges may streamline and manage their interactions with prospective and present students, faculty, alums, and staff. A centralized database stores essential data about each student, including their name, gender, educational background, contact details, email address, and more, streamlining the process of retrieving this data and making it possible to engrave and customize it, as well as the network used to deliver it to the student in real time. Everything related to a customer, from their contact information to the updates and deletions that have been made, is stored in a central database.
Faster customer service is only one of the many ways in which customer relationship management (CRM) may benefit educational institutions. Emails and other forms of communication may be automated, which speeds up response times and reduces workloads. It's useful for picking up on a variety of patterns, which may then be used as feed-back on matters like university admissions, promotions, and new department openings. In addition to archiving reliable data, this method aids universities at times of decision making, improvement, and data restoration[2]. Similarly, CRM automated workflow to aid in answering all inquiries and automatically assigning assignments to relevant employees. Using the monitoring features provided by CRM, universities may learn which websites prospective students have visited in their search for a suitable educational institution. This information can then be used into budgetary and resource allocation decisions.
Page  PAGE 10
2.2 Feasibility Analysis
	Customer relationship management (CRM) is a reprimand used in all types of organisations, including businesses, institutions, and educational establishments, with the goal of automating and refining business processes related to enhancing the company's connection with its clientele in the areas of service delivery, management, sales, and support. Westminster University's digital event management utilizes a customer relationship management (CRM) system. They saw enhanced usability, time savings, and the delivery of high-quality data for use in advertising. In order to streamline the registration process, they use a customer relationship management (CRM) solution to manage digital reservation forms, authorization, and reminder emails, and provide digital media such as tablets for scanning barcode registrants. Without CRM, they estimate that it would take several days to gather data following an event,

Specification and Design Cohort: D Group: 1 Group members: ABC 123 (Team leader) XYZ 456 Document Acceptance and Release Notice This document is authorised for release once all signatures have been...

1. Executive Summary

2. Specification

2.1 System Description

2.2 Feasibility Analysis

2.2.1 Technical Feasibility

2.2.2 Economic Feasibility

2.2.3 Organizational Feasibility

2.3 Requirements Specification

2.3.1 Functional

2.3.2 Non-functional

2.4 Use Cases

2.4.1 Use Case Diagrams

2.4.2 Use Case Descriptions

2.5 Context Model

3. Design

3.1 Architectural Design

3.2 Hardware Specifications

3.3 Database Structure

3.4 Interface Design

3.5 Sequence Diagrams

3.6 State Diagrams

4. References

Solution

Answer To This Question Is Available To Download

Related Questions & Answers

Submit New Assignment

Criteria (used as a guide only)	Exceeds Expectations (100% - 80%)	Meets Expectations (80% -70%)	Approaches Expectations (70% - 50%)	Does Not Meet Expectations (50%- 0%)
Other Evaluation
Executive Summary
Document format
Connectedness between Sections
Completness

Specification
System Description
Feasibility Analysis
Requirements Specification
Use Cases
Context Model
Misc elements

Design
Architectural Design
Hardware Specifications
Database Structure
Interface Design
Sequence Diagrams
State Diagrams
Misc elements

Grammar
Spelling is satisfactory
Grammatical expression is satisfactory