Software System Project

Project: <Church System>

Software Engineer: <Rabin Awal>

1. What is the Problem? (One sentence)

Need a system to manage daily operations of a Church and track visitor’s records.

2. Who are the Stakeholders? (List and identify what each wants)
Pastors
Staffs
Volunteers
Community
Sponsors

3. What are the Functional Requirements? (List)

Administrator should be able to do following
Add, Edit, Delete Pastors
Add, Edit, Delete Visitor’s detail
Add, Edit, Delete Volunteer’s details
Add, Edit, Delete staffs
Add, Edit, delete Sponsors
Add, Edit, delete Events
Add, Edit, Delete Activities
Add, Edit, delete Sermons

4. What are the non-Functional Requirements? (List)

 Usability – Easy to use menu and UI elements
 Reliability - should be accurate
 Performance – should response quick
 Supportability – should be easy to maintain and cross platform
 Implementation – Web and mobile
 Interface – web browser and mobile
 Operations – ease of use and non technical users could use
 Packaging – downloadable and installable
 Environmental - temperature
 Training - Online help, customer service, FAQ
 Legal Laws, Regulations, patents, data security
 Ethical

5. Create a System Flow (with Swim lanes) of the major process.

6. What are Use Cases? (List with name, description and actors)

Name Add Pastors

Description Administrators should be able to add pastors

Actor(s) Administrators
Flow of Events 1. Views to check pastor is not already in the system
2. Click Add Pastor
Special
Requirements
Pre- Conditions An Administrator should be logged
Post- Conditions New pastor’s details should be added into the database
Exceptions No double entry of same Pastor

Name Edit Pastor

Description Administrator should be able to update pastor’s details
Actor(s) Administrator
Flow of Events 1. Views the list of pastors
 2. Selects a pastor to update
3. Change the details
Special
Requirements
Pre- Conditions Admin should be logged in
Post- Conditions Pastor’s detail is updated with new information
Exceptions
No new entry should be made for edits

Name Delete Pastor

Description Administrator should be able to remove pastor
Actor(s) Administrator
Flow of Events 1. Views the list of pastors
2. selects a pastor to be remove
3. Delete the pastor
Special At one time, one pastor should be removed
Requirements
Pre- Conditions Administrator should be logged in
Post- Conditions A Pastor is removed and the list is updated
Exceptions

Name Add a Visitor

Description Administrators should be able to add a visitor's details

Actor(s) Administrators
Flow of Events 1. Check to see if the visitor exist in the system
2. Click add visitor
3. Fill the details of the visitor
4. Submit the form
Special
Requirements
Pre- Conditions An Administrator should be logged
Post- Conditions New visitor’s information should be added into the database
Exceptions No double entry of same visitor

Name Edit a Visitor

Description Administrator should be able to update visitor's details

Actor(s) Administrator
Flow of Events 1. Views the list of visitors
2. Selects a pastor to update
3. Change the details
 4. Click Update
Special
Requirements
Pre- Conditions Admin should be logged in
Post- Conditions visitor’s detail is updated with new information
Exceptions
No new entry should be made for edits
No double entry of same visitor

Name Delete a Visitor

Description Administrator should be able to remove a visitor’s detail
Actor(s) Administrator
Flow of Events 1. Views the list of visitors
2. selects a visitor to be remove
3. Delete the visitor
Special At one time, one visitor should be removed
Requirements
Pre- Conditions Administrator should be logged in
Post- Conditions A visitor is removed and the list is updated
Exceptions

Name Add a Staff

Description Administrators should be able to add a staff's details

Actor(s) Administrators
Flow of Events 1. Check to see if the staff exist in the system
2. Click add staff
3. Fill the details
4. Submit the form
Special
Requirements
Pre- Conditions An Administrator should be logged
Post- Conditions New staff’s information should be added into the database
Exceptions No double entry of same staff

Name Edit a staff

Description Administrator should be able to update staff's details

Actor(s) Administrator
Flow of Events 1. Views the list of staffs
2. Selects a staff to update
3. Change the details
 4. Click Update
Special
Requirements
Pre- Conditions Admin should be logged in
Post- Conditions staff’s detail is updated with new information
Exceptions
No new entry should be made for edits
No double entry of same staff

Name Delete Staff

Description Administrator should be able to remove a staff’s detail
Actor(s) Administrator
Flow of Events 1. Views the list of staffs
2. selects a staff to be remove
3. Delete the staff
Special At one time, one staff should be removed
Requirements
Pre- Conditions Administrator should be logged in
Post- Conditions A staff is removed and the list is updated
Exceptions

Name Add a Sponsor

Description Administrators should be able to add a sponsor's details

Actor(s) Administrators
Flow of Events 1. Check to see if the sponsor exist in the system
2. Click add sponsor
3. Fill the details
4. Submit the form
Special
Requirements
Pre- Conditions An Administrator should be logged
Post- Conditions New sponsor’s information should be added into the
database
Exceptions No double entry of same sponsor

Name Edit a Sponsor

Description Administrator should be able to update sponsor's details

Actor(s) Administrator
Flow of Events 1. Views the list of sponsors
2. Selects a sponsor to update
 3. Change the details
4. Click Update
Special
Requirements
Pre- Conditions Admin should be logged in
Post- Conditions Sponsor’s detail is updated with new information
Exceptions
No new entry should be made for edits
No double entry of same sponsor

Name Delete Sponsor

Description Administrator should be able to remove a sponsor’s detail
Actor(s) Administrator
Flow of Events 1. Views the list of sponsor
2. selects a sponsor to be remove
3. Delete the sponsor
Special At one time, one sponsor should be removed
Requirements
Pre- Conditions Administrator should be logged in
Post- Conditions A sponsor is removed, and the list is updated
Exceptions

Name Add an Event

Description Administrators should be able to add an event

Actor(s) Administrators
Flow of Events 1. Check to see if the event exist in the system
2. Click add event
3. Fill the details
4. Submit the form
5. Publish the event
Special
Requirements
Pre- Conditions An Administrator should be logged
Post- Conditions New events information should be added into the database
Exceptions No double entry of same event

Name Edit an Event

Description Administrator should be able to update event's details

Actor(s) Administrator
Flow of Events 1. Views the list of events
 2. Selects an event to update
3. Change the details
4. Click Update
Special
Requirements
Pre- Conditions Admin should be logged in
Post- Conditions Sponsor’s detail is updated with new information
Exceptions
No new entry should be made for edits
No double entry of same event

Name Delete Event

Description Administrator should be able to remove a sponsor’s detail
Actor(s) Administrator
Flow of Events 1. Views the list of events
2. selects an event to be remove
3. Delete the event
Special At one time, one event should be removed
Requirements
Pre- Conditions Administrator should be logged in
Post- Conditions An event is removed and the list is updated
Exceptions

Name Add Activities

Description Administrators should be able to add church activities

Actor(s) Administrators
Flow of Events 1. Views to check activity is not already entered in the
system
2. Click Add Activity
Special
Requirements
Pre- Conditions An Administrator should be logged
Post- Conditions New activity information should be added into the database
Exceptions No double entry of same activity

Name Edit Activities

Description Administrator should be able to update an activity
Actor(s) Administrator
Flow of Events 1. Views the list of church daily activity
2. Selects an activity to update
3. Change the details
Special
Requirements
Pre- Conditions Admin should be logged in
Post- Conditions Activity detail is updated with new information
Exceptions
No new entry should be made for edits

Name Delete Activities

Description Administrator should be able to remove an activity
Actor(s) Administrator
Flow of Events 1. Views the list of activities
2. selects an activity to be remove
3. Delete an activity
Special At one time, one activity should be removed
Requirements
Pre- Conditions Administrator should be logged in
Post- Conditions An activity is removed, and the list is updated
Exceptions

Name Add Sermon

Description Administrators should be able to add a sermon

Actor(s) Administrators
Flow of Events 1. Views to if the sermon is already in the system
2. Click Add Sermon
Special
Requirements
Pre- Conditions An Administrator should be logged
Post- Conditions New sermon’s details should be added into the database
Exceptions No double entry of same Sermon is granted

Name Edit Sermon

Description Administrator should be able to update sermon’s details
Actor(s) Administrator
Flow of Events 1. Views the list of sermons
2. Selects a sermon to update
3. Change the details
Special
Requirements
Pre- Conditions Admin should be logged in
Post- Conditions Sermon’s detail is updated with new information
Exceptions
 No new entry should be made for edits

Name Delete Sermon

Description Administrator should be able to remove a sermon
Actor(s) Administrator
Flow of Events 4. Views the list of sermons
5. selects a sermon to be remove
6. Delete the sermon
Special At one time, one sermon should be removed
Requirements
Pre- Conditions Administrator should be logged in
Post- Conditions A Sermon is removed and the list is updated
Exceptions

7. Identify the architectural pattern(s) used for this system

Client- Server Architecture

8. List the Screens (with actions that can be done from those screens)
i) Pastors list – Add, Edit or Delete Pastor
ii) Events list - Add, Edit or Delete an Event
iii) Activity List - Add, Edit or Delete an Activity
iv) Sermons list - Add, Edit or Delete a sermon
v) Staffs list - Add, Edit or Delete Staff
vi) Sponsors list - Add, Edit or Delete a sponsor

9. Provide Object Model (Class Diagram)

a. Attributes (with data type starting Lesson 3

b. Operations (with signature and return type starting Lesson 3)
c. Associations – with label and multiplicity