I need help with a Software Engineering assignment

MCIS 6153: Software Engineering - Project Due Date: July 26th, 2019 Description: You have been asked to build an admin portal that will allow your company internal employees to access the portal and perform admin functions on behalf of company clients. Here are additional details:

a) Admin portal is accessible only on company network to only company employees. b) Access to the links is role based i.e. only authenticated internal employees with appropriate role/s are

able to access the portal. What links you can access once on the portal is determined based on what other roles you have. So, same link will not be visible to another admin who doesn't have appropriate role to access the link.

c) There are five categories of applications and 5 admin roles. Here are the details:

Category Role Access Links

Global ADMIN All Global links Manage User Accounts, Assign Roles, Help Desk

Finance FINANCE_ADMIN All Global links + All Finance Category links

Finance Reports, Accounts Payable, Accounts Receivables, Tax

Sales SALES_ADMIN All Global links + All Sales Category links

Sales Reports, Sales Leads, Sales Demo

HR HR_ADMIN All Global links + All HR Category links

Employee Management, Benefits, Payroll, HR Reports

Engineering ENGG_ADMIN All Global links + All Engineering Category links

Application Monitoring, Tech Support, App Development, App Admin, Release Management

(d) Links redirect users to the admin application that is not developed by you. Deliverables: Provide project planning tasks document (5-10 pages) related to above requirements. Document must include:

• Project scope and requirements (functional and non-functional) • Risk analysis and recommendations • Resourcing plan • Implementation plan (discuss development methodology, technologies, etc.) • Project schedule (Iterative and what are deliverables for each iteration / sprint) • Solution architecture (Show all required components i.e. frontend, backend, dependencies, db, etc.) • Provide User Stories / Scenarios with effort estimate (large, medium, low), resources count (developer

+ tester), target release for each story. I recommend using a table. • Make sure you provide enough stories to cover 100% functional requirements.

Story format: actor, action, outcome Story example: "As an internal admin, I should be able to access the Admin Portal, so I can perform admin functions."

• Testing plan • Quality measurement plan • Deployment plan • Maintenance plan

NOTES: - Make sure to check for plagiarism before submission. If your document is more than 25% copied, you

will receive a ZERO. - We are not implementing the system as summer semester is short. - This is not a group project. You have to work individually.

What to turn in:

- Only soft copy uploaded to blackboard on or before due date. - No extensions.