MSC Fileman 22.2

Back in the Saddle

After a year of working to provide market research for VA's emerging Fileman Evolution projects - especially after OSEHRA's December sprint to upgrade MSC Fileman 22.2 in support of VA's test-plan contract with Leidos, and the January VISTA Community Meeting in Sacramento - my health finally collapsed for six weeks of February and March. I returned to the office just in time to watch VA's next Fileman 22.2E testing contract sail over the plate before I could respond to it, much to my dismay and disappointment.

MSC Fileman 22.2 Patches

One of the characteristics of the final stage of packaging a new version for a VISTA application is that we must paradoxically freeze development without freezing development.

We must freeze development because the distribution sent to the world has to be a specific, tested version of the software. Getting to that point requires constraining development toward satisfying the results of testing, not introducing new disruption late in the packaging process, when there won't be sufficient time to test it. In this pro-testing era, most people get this issue pretty well.

FLAP Phase Two Prep Status Update: Name Change and KIDS Bug

With prep for and recovery from the VISTA Community Meeting in Sacramento, it's a good time to jump back into our series of blog posts about FLAP Phase Two Prep, which has continued through this period.

On 5 January we delivered a preview RSA file of MSC Fileman 22.2V3 to VA so their MSC Fileman 22.2 intake contract with Leidos could shift to the refreshed codebase. Since then I've been working on verification, cleanup, and packaging to prepare to distribute MSC Fileman 22.2 to the rest of the community.

About the FLAP Phase Two Prep Sprint

Yesterday, we completed the monthlong, intensive sprint to update our first release of Fileman 22.2 from March 2013 to produce MSC Fileman 22.2. We in this case consisted of Don Creaven, Zach Gonzales, George Timson, Sidney Tarason, David Whitten, OSEHRA Product Manager Mike Henderson, and me, with FLAP documenter Kathy Ice working in parallel on the manuals (see below) and FLAP system manager David Wicksell working hard to keep our servers accessible during this period of trials and tribulations. The focus of this update was on:

FLAP and Fileman's Architectural Role

To say that File Manager is VISTA's database management system is a gross understatement, so gross that it is more misleading than helpful.

Traditional database systems run side by side with the applications, offering data-related services (like creating, reading, updating, and deleting records - the services with the unattractive acronym CRUD - along with many, many other such services). In other words, most DBMSes have a peer-to-peer relationship with the applications that use them to manage their data.

Subscribe to RSS - MSC Fileman 22.2