Project Analysis – Step 2 (Software & Multimedia)

🖥️ Project Analysis – Step 2 (Software Projects)

Focus: Identifying users (actors), defining functional & non‑functional requirements, and building use cases.

1) Identify System Users (Actors)

After your initial research, determine who will interact with the system. In software engineering, these are actors—they can be people or external systems.

Primary actors: Directly use the system to achieve a goal (e.g., Customer, Admin).
Secondary actors: Support or integrate with the system (e.g., Payment Gateway, Email Service).

Example – Online Shopping: Customer (primary), Admin (primary), Payment Gateway (secondary), Inventory System (secondary).

2) Functional Requirements (What the system does)

The system shall allow users to register, log in, and manage their profiles.
Users shall be able to search, filter, and view detailed items.
Admins shall add, edit, and delete items and categories.
The system shall support checkout and payment processing.

3) Non‑Functional Requirements (How the system performs)

Performance: Home page loads within 3 seconds under normal load.
Usability: Works on desktop and mobile; accessible with keyboard navigation.
Security: Role‑based access, encrypted connections, data privacy compliance.
Reliability: 99.5% uptime target; graceful error handling and retries.
Scalability: Supports growth in users, products, and traffic.

4) Use Case Table (Sample)

Use Case ID	UC‑01
Use Case Name	Place an Order
Actor	Customer
Description	Customer selects items, provides shipping details, confirms payment.
Preconditions	User is logged in; cart has at least one item.
Trigger	User clicks “Checkout”.
Main Flow	1) System shows checkout → 2) User enters shipping → 3) User selects payment → 4) System processes payment → 5) Order confirmed.
Postconditions	Order stored; confirmation email sent.
Exceptions	Payment failure; out‑of‑stock item.

Tip: Repeat this table for each major use case (Search, Manage Products, Process Refund, etc.).

5) Use Case Diagram (What to include)

Actors: Customer, Admin, Payment Gateway
Use Cases: Login, Search Product, Add to Cart, Checkout, Process Payment, Manage Products
Relationships: Connect each actor to the use cases they initiate or participate in.

Placeholder: Insert your UML use case diagram image here once designed (e.g., exported from draw.io, Lucidchart, or StarUML).

6) Why this step matters

Clarifies system scope and prevents missed features.
Aligns team understanding with real user needs.
Creates a concrete reference for design, development, and testing.

🎬 Project Analysis – Step 2 (Multimedia Projects)

Focus: Identifying characters, defining environments, and sketching scenes for overall visual design.

1) Identify Characters

Define who appears in the story or experience. Characters drive narrative and engagement.

Main characters: Central to the story; most screen time.
Supporting characters: Advance the plot, provide context or guidance.
Background characters: Populate the world with minimal direct impact.

Example – Educational Animation: Curious child scientist (main), friendly robot helper (main), teacher & classmates (supporting), pedestrians & wildlife (background).

2) Identify Environments (Settings)

List the locations and visual contexts where scenes take place.

Primary locations: Core settings (e.g., science classroom, lab).
Secondary locations: Occasional scenes (e.g., schoolyard, nature reserve).
Transition/background: Scene changes, establishing shots (e.g., city street, library).

3) Scene Sketching & General Design

Sketches help align the artistic vision before production.

Character concept sketches: Poses, expressions, costumes.
Environment layouts: Room maps, perspective backgrounds.
Storyboards: Sequential frames showing composition, camera movement, and timing.

Example Workflow: Sketch main characters → Draw lab layout → Storyboard a short scene about the solar system using a hologram prop.

4) Production Readiness

Create a shared style guide for colors, line weights, and typography.
Define naming conventions for assets (characters, props, scenes).
Agree on deliverable formats (PNG/EXR for art, layered files, animatics).

5) Why this step matters

Ensures consistent visual language across the production.
Reduces late‑stage redesigns by aligning expectations early.
Improves collaboration between writers, designers, and animators.