1.

Actors of the given system:

Lee Wen (CEO): Responsible for negotiating contracts, estimating project time and fees, managing
project leaders, and reconciling discrepancies.

Clients: Approach Lee Wen for software services and negotiate project requirements.

Project Leaders: Appointed by Lee Wen to manage projects, file project status reports, and oversee
project phases.

Team Members: Assigned to project teams, work on software development phases, and file time sheets.

2. Activities from the perspective of the roles:

Lee Wen (CEO):

 Negotiate contracts with clients.

 Estimate project time and fees.
 Appoint project leaders and team members.
 Reconcile discrepancies between project status reports and time sheets.

Project Leaders:

 File project status reports.

 Monitor the completion status of each phase.
 Track person-hours spent on each phase.
 Communicate with team members and reconcile discrepancies.

Team Members:

 Work on software development phases (Requirements analysis, Design, Coding, Testing).

 File time sheets specifying project details and time spent.

3. DSDM Phases and Activities:

DSDM (Dynamic System Development Method) is an iterative and incremental approach to software
development. From the given scenario, the following phases and activities can be identified:

Feasibility Study:

Assess the feasibility of the project.

Determine if the project aligns with the MNC's goals and capabilities.
Business Study:

Gather and analyze client requirements.

Identify software specifications.

Determine the project's identification number and name.

Functional Model Iteration:

Perform requirements analysis.

Define software specifications.

Identify functional requirements.

Design and Build Iteration:

Design the software solution.

Develop the software code based on the design.

Implement the software solution.

Implementation:

Perform software testing.

Conduct user acceptance testing.

Finalize the software for deployment.

4. MoSCoW activities of the given business case:

MoSCoW stands for Must have, Should have, Could have, and Won't have. Based on the given business
case, the MoSCoW activities can be defined as follows:

Must have:

Negotiating contracts with clients.

Estimating project time and fees.

Filing project status reports.

Tracking person-hours spent on each phase.

Paying salaries based on working hours.

Should have:

Appointing project leaders and team members.

Analyzing client requirements.

Performing software testing.

Reconciling discrepancies between project status reports and time sheets.

Could have:

Monitoring project progress.

Performing user acceptance testing.

Conducting feasibility and business studies.

Designing and building the software solution.

Won't have:

Detailed financial analysis.

Extensive documentation of every project phase.

5. Timebox with activities and milestones:

Assuming a weekly timebox, the activities and milestones can be structured as follows:

Timebox: One Week

Milestones:

Negotiate contracts and finalize project details with clients.

Appoint project leaders and team members.

Complete project status reports and reconcile any discrepancies.

File time sheets and track person-hours spent on each project.

Activities:

Feasibility assessment

Business requirements gathering

Requirements analysis and software specifications (RASS)

Software design

Software coding

Software testing

Salary calculation and payment

Generation of weekly reports (project progress, employee time spent)