Setup Dev Environment for UI

[JustKuzya]

User Story:

##As an OSCAL Developer, I need to be able to:

1. Set up NODE/ANGULAR environment
2. Track and manage all JavaScript libraries, frameworks, and tooling (i.e.dependencies) with YARN
3. Create a basic mock-up of the browser-based UI in Model-View-Controller paradigm

Goals:

1. Have a reproducible way to set-up developer environment
2. Have easier management of JavaScrip dependencies
3. Have a browser based UI layout
4. Have UI infrastructure for capturing/validating user input
5. Have working proof-of-concept to persist the captured data

Dependencies:

No dependencies: new issue

Acceptance Criteria

1. Working installation for local environment deployment
2. Working browser-based UI

[anweiss]

@JustKuzya would you mind providing a bit more info in the issue? Are you looking for UI samples that are built with Node.js and JavaScript? Or are you looking for a more prescriptive approach to OSCAL-based UI development?

[bradh]

I don't think that OSCAL schemas / data models requires a UI (in Node/Angular, or C# or whatever). A separate project to provide some data entry thing could be useful, but that seems outside the scope of this project.

@JustKuzya are you planning to develop something like that?

[david-waltermire]

Yeah. We share an office at NIST. He is going to start working on a browser-based tool. I had asked him to submit an issue for getting the environment setup for development. We will probably do this work in another repo.

[bradh]

Sounds good. In terms of dependencies, clearly it depends on stability of the OSCAL schema(s) you're working with, so Catalog / Profile looks better than Assessment layer at this stage.

[JustKuzya]

We hope to have basic UI for OSCAL formatted information collection and basic workflow allowing OSCAL users to perform: catalog(s) -> baseline selection, controls customization, persisting intermediate steps, etc. We target a browser-based implementation for that. This effort is meant to be a simple UI<->OSCAL mapping/persistence mock-up. The main goal is to flush out potential “oopsies” in OSCAL, if any. The UI mockup does not intend any assessor/tech/admin roles assignment/actions validation/duities distribution for workflow actions mapping as it usually would happen in a bigger organizations. The mockup means to validate OSCAL’s ability to support building UI from the OSCAL schema-defined data, store and validate user input, and leverage OSCAL to the max to test the limits. DC From: anweiss <notifications@github.com> Sent: Thursday, January 23, 2020 5:26 PM To: usnistgov/OSCAL <OSCAL@noreply.github.com> Cc: Cousin, Dmitry A. (Fed) <dmitry.cousin@nist.gov>; Mention <mention@noreply.github.com> Subject: Re: [usnistgov/OSCAL] Setup Dev Environment for UI (#606) @JustKuzya<https://github.com/JustKuzya> would you mind providing a bit more info in the issue? Are you looking for UI samples that are built with Node.js and JavaScript? Or are you looking for a more prescriptive approach to OSCAL-based UI development? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#606?email_source=notifications&email_token=ACS6IVUEWLGYNB3RPEISX7TQ7IKPVA5CNFSM4KKYZAXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJZCTUA#issuecomment-577907152>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACS6IVRLNIQF5EL22LIPEATQ7IKPVANCNFSM4KKYZAXA>.

[wendellpiez]

March 12 Update

@JustKuzya will update with current progress. Much learning. Angular.

[JustKuzya]

2020-03-12

Going through a learning curve. Trying to do the right design to not overwrite too much later on. Currently muscling through the book Angular: Your First Week and the latest Angular Docs Site.

[david-waltermire]

@JustKuzya Please provide a link to a public Github repo in a comment on this issue once you get to that point.

[david-waltermire]

@mocolicious Thanks for creating a new Repo. Appreciate your efforts on this. Closing this issue.