A Guide to Harnessing WRSPM Effectively

A Guide to Harnessing WRSPM Effectively

·

2 min read

Remember that SDLC stands for Software Development Life Cycle? In the last article, we talked about Requirements & Specifications, and a cool model called WRSPM. Today, we'll dive deeper into WRSPM and see how we can use it to prepare requirements and specifications for a fitness app we've been tasked to build.

WRSPM's Hidden Gems

  • EH (Elements Hidden from the System): Imagine a bridge between users and the app. EH considers things the app can't directly see, like user goals or tech skills. This ensures an app that works for everyone!

    • Example: EH tells us users might want to track steps, distance, calories, and sleep. It also emphasizes user-friendliness, security, and battery efficiency.
  • EV (Elements Visible to the System): These are the things the app interacts with directly, like buttons, menus, and sensors.

    • Example: EV helps design clear buttons, menus, and displays for easy user interaction.
  • SV (Elements Shared between System and Environment): This is how the app interacts with the outside world, like exchanging data with the user.

    • Example: SV helps design ways for users to easily enter and see data through taps, swipes, or voice commands.
  • SH (Internal Representation of Data): This is all about how the app stores and uses data efficiently.

    • Example: SH helps design ways to store user data and use algorithms to analyze it and create reports.

Fitness App Requirements and Specifications

By applying WRSPM, we can derive specific requirements and specifications for our fitness app:

Requirements:

  • Functional: Track key metrics like steps, distance, calories burned, and sleep patterns.

  • Non-Functional: Prioritize user-friendliness, robust security, and low battery consumption.

Specifications:

  • User Interface Layout: Tailor interface based on user characteristics (beginner, advanced) for easy navigation.

  • Data Collection Methods: Adapt data collection based on user activity levels (running vs. walking) and technical expertise (phone vs. wearable).

  • User Interface Design: Clear buttons, intuitive menus, and informative displays for user engagement.

  • Data Display and Input: Efficient exchange of information between the app and the user through taps, swipes, and voice commands (accessibility).

  • Data Storage: Efficient storage mechanisms for tracking large amounts of user data (steps, sleep cycles).

  • Data Processing: Algorithms for analyzing user metrics (distance, calories) and generating reports (progress charts).

WRSPM provides a comprehensive approach to bridge the gap between requirements and development, fostering a clear understanding and ultimately, a successful fitness tracker app.

Join us on Friday as we explore the Design Phase of SDLC and all it entails! Do you have any questions about WRSPM? Share them in the comments below!