Feedback on requirements engineering student assignments using the OpenMRS project

[twinkleflip (Birgit Penzenstadler)]

Hi all

I’m a professor for software engineering at CSULB in California, USA, intro here. As mentioned here, last semester I taught a course on Requirements Engineering using HFOSS and had students do their assignments using the project documentation of OpenMRS.

I am not sure how helpful these requirements models and analysis reports can be for you but I’d like ot ask for some community feedback, because I will be teaching this course again Jan-May 2018 and would like to modify the assignments in a way (or also create some new ones) that the results contribute something meaningful and helpful to OpenMRS. Actually the more assignments the merrier because you don’t need 5 different solutions (by my student teams) to the same task but would rather have 5 tasks done.

The assignments (and example solutions) that used OpenMRS project documentation were:

• (Re-)Engineering a stakeholder model and example solution
• (Re-)Engineering goals and example solution
• (Re-)Engineering a system vision and example solution
• (Re-)Engineering a domain model (we ended up skipping this one, so no example solution)
• (Re-)Engineering use cases and example solution
• (Re-)Engineering Quality requirements and example solution

What I am looking for:

• Any feedback as to how we can turn this into useful contributions for the project would be appreciated.
• Any suggestions for or pointers towards other tasks you may want contributors to that have to do with requirements engineering, requirements analysis, user analysis, user modeling, or the likes would be appreciated.

Kind regards, Birgit

[dkayiwa (Daniel Kayiwa)]

We are planning releases for the next version of the platform and reference application. Do you see ways in which your students can contribute towards requirements engineering for these? Even if it is just advising us on how to improve our requirements engineering process for subsequent releases, it will still be a very valuable contribution!

The two threads below will give you some details regarding how we are collecting these requirements:

Platform 2.2 Planning

We need to get a release of the Platform out soon. OpenMRS Core 2.1.0 was released in April 2017 without a corresponding Platform release, so the next release of the Platform will be version 2.2. Per the Platform Vision, we would like not only to bring add new features to the Platform, but also incorporate some of the modules which are used by nearly every implementation. Current candidates for Platform 2.2: Incorporate the Idgen Module into the Platform. Add Encounter Diagnoses (TRUNK-5015) …

Reference Application 2.7 Planning, Ideas, Features and Road Map

Continuing the discussion from Reference Application 2.6.0 Is Released.: Now that Ref App 2.6 is out, it is time to shift gears to 2.7 which will be released in October 2017. As an implementor what do you want to see in this release - what are your top 5 asks? As a developer who is customizing and extending Ref App - what advances do you want to see? As a user, hospital, health facility, doctor - what do you want to see in the next release? The approach for 2.7 will follow similar m…

These other two links could also give you some sense of how we have been doing our road map: https://wiki.openmrs.org/display/docs/Technical+Road+Map https://wiki.openmrs.org/display/projects/Reference+Application+Road+Map

Then this other thread will give you some bits for the bahmni openmrs distribution:

Help define the short-term Bahmni Roadmap

Background As you’ve all probably seen, we’re in the midst of transforming Bahmni from being a ThoughtWorks-owned project, to being a true FOSS project, with a coalition of organizations and individuals collaborating on its software development. In early October, in just a few weeks, we will be spinning up a new iteration of the development team, and with this, we’ll be putting together a new Road Map. In the medium-term, we’ll have a more formal Roadmap process (which is very underspecified i…

Just in case you want to look at this too: Log In - OpenMRS Wiki

[twinkleflip (Birgit Penzenstadler)]

@dkayiwa Yes, I see some opportunities there. The next class is Jan-May 2018 so we should plan requirements engineering tasks for that. It looks like your next release is planned for this month, but the timeline further ahead is not scheduled yet, or at least not on the Roadmap as far as I can see. Is that correct? I know that my planning is long-term but that’s how university courses work Would you be able to give me a rough estimate on the further timeline for Jan-May 2018?

For any contributions over the next 7-8 weeks, I would have to cover something in the topics listed in my previous thread on advanced software engineering, like maintenance, security, and resilience. Suggestions still appreciated for that course.