Date: Fri, 29 Mar 2024 13:46:41 +0000 (UTC) Message-ID: <1904359752.27.1711720001768@8699a9c6e1d1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_26_632946166.1711720001768" ------=_Part_26_632946166.1711720001768 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Our goal for Phase 1 of the Ar= cLight information architecture process was to identify the primary types o= f users and establish a core set of requirements that could be used to info= rm the design work in later phases of the overall design process for ArcLig= ht. The two primary artifacts developed during this phase were a set of personas, derived from data gathered during user intervie= ws and analyzed further upon their completion, and a set of requirements with a draft prioritization used as the basis for discuss= ion with stakeholders.
Staff from Stanford University= Libraries, University of Michigan, and Georgia Tech developed six personas= period:
Discussion with stakeholders a= t at Stanford University Libraries also led us to identify a set of additio= nal needs for curators, related to both using archival descriptions and mat= erials like subject guides to help present an institution's collections to = support their acquisition function, as well as the development of interpret= ive materials, including online exhibits.
We developed the requirements = following the completion of the personas. The requirements were informed by= the personas, in addition to in-depth review of the user interview analysi= s and other stakeholder documents provided to us during ArcLight Discovery: Phase 1. We prioritized the= requirements using the MoSCoW method (M= ust have; Should have; Could have; and&nbs= p;Won't have) to inform the scope of work for an upcoming work cyc= le led by Stanford to produce a minimum viable product.
Personas
Requirements