ninjanatethegreat.files.wordpress.com · web viewin 1970, kirkland lorey irvis organized a...
TRANSCRIPT
P a g e | 0
PBCOhe phasesNate Franklyn, Tyesha Day, Kneil Lindo
Team TNK
P a g e | 1
Overview
In 1970, Kirkland Lorey Irvis organized a conference along with other professionals to
address the success of African Americans continuing on to a higher education. After this
conference, the Pennsylvania Black Conference on Higher Education (PBCOHE) is our client and
this organization was created for graduate students and professionals. The PBCOHE annual
conference provides training and opportunities for the progression of underrepresented individuals
in higher education.
The problem with the existing website that PBCOHE has developed is that the website is
out-of-date; members and professionals who want to attend upcoming conferences cannot find
information of when an event is set to begin or going on. Another problem prominent in the site is
the notion of attending an event, when a user register or pay for the event that user is advised to
print out a paper and hand it in with his or her payment. This is an issue due to the fact that by
doing this the organization is neglecting users who may not be able to reach member or the office.
The PBCOHE website also is dark and dull, which can be unentertaining to a prospective sponsor
or member. Lastly in addition to all these issues, the current product does not provide support for
PDF file viewer for integration of the PBCOHE Newsletter.
The main elements that PBCOHE want to keep their logo and pictures. The client wants to
add a calendar to allow users to view events for each month and register for an event online. The
client also wants more people to join as members and to have more sponsors join the organization.
The solution to this existing product is to create a website that will keep the logo of PBCOHE and
pictures, but brighten up the website. What we plan on adding is an online application to register for
a conference, an online payment plan system, and a calendar to let people know what the upcoming
P a g e | 2
events for each month are. The best tool we feel that will help us be successful is WordPress,
because it is easy to manage, easy to adapt existing systems and structures to, easy to learn and easy
to add comments and structure. WordPress is a publishing system that uses PHP and MySQL. This
free software is allows users unlimited control. This publishing system has many widgets, plugins,
and themes with minimum requirements.
We plan to attract graduate students, sponsors, and undergraduate students to understand
who PBCOHE is, what they are doing for the community, and how people can join. Our team has
experience in website development and we will up-date the website through posting on social media
and marketing to users. We each have something that we can contribute such as using WordPress to
manage a personal website. We have researched PBCOHE thoroughly and met the key contacts, in
part Barbara Thompson.
Our group plans on achieving our client’s requirements and attracting underprivileged
students who plan to pursue higher education. By adding the addition of interactive tools and other
details discussed above, we will meet the user experience goals.
P a g e | 3
Table of ContentsPHASE 0: PROBLEM SPACE...............................................................................................................................6
Organizational Analysis...................................................................................................................................6
User Characteristics..........................................................................................................................................8
Problem Space..................................................................................................................................................9
Assumptions and Claims................................................................................................................................11
Initial Assumptions and claims...................................................................................................................11
Reformulated Assumptions and claims......................................................................................................11
Inspiration......................................................................................................................................................13
Motivation..................................................................................................................................................13
Project Plan....................................................................................................................................................13
Team Roles and Task Assignments............................................................................................................15
References......................................................................................................................................................16
PHASE 1: REQUIRMENTS GATHERING AND ANALYSIS....................................................................................17
User Profiles...................................................................................................................................................17
Personas.........................................................................................................................................................23
Functional Requirements...............................................................................................................................25
Non - Functional Requirements..................................................................................................................25
Data Requirements........................................................................................................................................27
Context of Use Requirements........................................................................................................................28
Social Environment.....................................................................................................................................28
Organizational Requirements.....................................................................................................................28
Technical Requirements.............................................................................................................................29
Task Analysis..................................................................................................................................................30
HTA Diagram..............................................................................................................................................31
Data Gathering...............................................................................................................................................32
Usability goals................................................................................................................................................33
User Experience Goals................................................................................................................................33
PHASE 2: DESIGN ALTERNATIVES...................................................................................................................35
Project Description.........................................................................................................................................35
Key Requirements......................................................................................................................................35
Functional Requirements...........................................................................................................................36
Non-Functional Requirements...................................................................................................................36
P a g e | 4
Design Space..................................................................................................................................................38
Design Assessment.........................................................................................................................................39
Usability Goals............................................................................................................................................39
User Experience Goals................................................................................................................................40
Comparison of the Prototypes against the Criteria....................................................................................40
Summary/Reflection.......................................................................................................................................42
Teamwork......................................................................................................................................................43
Prototype Presentation..................................................................................................................................44
Prototype One - WordPress platform Codename “#1 Draft Pick”..............................................................44
Prototype Two - Weebly platform Codename “Training Wheels”..............................................................47
Prototype Three - Codename “Drawing board”.........................................................................................50
PHASE 3: SYSTEM PROTOTYPE AND EVALUATION PLAN................................................................................52
Project Description.........................................................................................................................................52
Requirements Summary.................................................................................................................................53
Functional...................................................................................................................................................53
Non-Functional...........................................................................................................................................53
Design Summary.............................................................................................................................................54
Prototypes......................................................................................................................................................56
Screenshot 1...............................................................................................................................................57
Screenshot 2...........................................................................................................................................57
Screenshot 3...............................................................................................................................................58
Screenshot 4...............................................................................................................................................58
Screenshot 5...............................................................................................................................................59
Screenshot 6...............................................................................................................................................59
Evaluation plan...............................................................................................................................................60
Goals...........................................................................................................................................................60
Questions that address these goals............................................................................................................60
Methods of Evaluation...............................................................................................................................61
Practical Issues...........................................................................................................................................62
Ethical Issues..............................................................................................................................................63
Summary/Reflection.......................................................................................................................................64
PHASE 4: EVALUATION...................................................................................................................................65
Overview........................................................................................................................................................65
P a g e | 5
Description of Methods, tasks, and users.......................................................................................................65
Design Rationale for Methods and Materials.................................................................................................67
Summary of Findings......................................................................................................................................68
Discussion of Results......................................................................................................................................69
Design Implications........................................................................................................................................70
Improvements................................................................................................................................................71
Critique...........................................................................................................................................................72
P a g e | 6
PHASE 0: PROBLEM SPACE
Organizational AnalysisThe Pennsylvania Black Conference on Higher Education, Inc. (PBCOHE) is an
organization made up of African Americans and other underrepresented professionals from the
public and private sector, education, business, social services, law, and government agencies that
have a deep commitment to improving and ensuring the education of underrepresented
students(Vision, P.1). Comprised of respected professionals from all walks of life; PBCHOE, has
been a major force in the underrepresented youth for more than forty years. From providing support
and “...professional development opportunities through its scholarship program, the annual
conference, the Robert D. Lynch Student Leadership Development Institute (SLDI), the Institute for
Educational Management and Leadership (IEML), and the Pennsylvania Black Conference on
Higher Education Journal”(Vision P.3). As well as giving a voice “to the various sectors of
government, education and community leaders that impact the lives of underrepresented groups at
Pennsylvania colleges and universities” (Vision P.3).
PBCOHE hold dozens of conferences and leadership panels throughout the year. Working
alongside a wide-range of university officials, business professionals, and public education leaders,
PBCOHE is able to reach out to the community and provide learning opportunities that educate &
build the next generation. PBCOHE also sends representatives out to understand and research the
changing underrepresented student population in higher education. “The mission of the
Pennsylvania Black Conference on Higher Education, Inc. (PBCOHE) is to provide programs and
services which help ensure that the post-secondary educational needs and aspirations of African
Americans in particular are met, and to work in concert with members of other underrepresented
groups in the Commonwealth.”(Mission, P.1)
P a g e | 7
As well as in addition to:
• Developing an educational environment that promotes and encourages desirable
educational advancement for all people and educational strategies to promote inter-group
understanding within an increasingly diverse population in the Commonwealth.
• Contributing to efforts in the Commonwealth to graduate students by promoting quality
programs which encourage personal and academic achievement and support efforts to recruit,
develop, and promote its faculty and staff, once hired, and by
• Creating a climate that promotes and attracts students to post-secondary education and
graduate programs. (Mission, P.3)
The currently implemented website is used to inform the users, attract sponsors, as well as
educate the public. In addition to this, the product is supposed to help student network by providing
them opportunities to flourish with like-minded individuals and peers. Potential challenges and
constraints include:
Being limited to what we may change or construct,
Review and criticism from the PBCOHE board members
Maximizing and determining the necessities
Teaching or educating an inexperienced administrator
Usability studies
We plan to provide the very best options and avenues of success by communicating with
PBCOHE as much as possible so the client may learn and get a feel for the system as it being
constructed.
P a g e | 8
User CharacteristicsThe site is mainly geared toward African American professionals who value higher
education. Our target users are professionals already in working in their career field, sponsors who
are looking to know what the Pennsylvania Black Conference of Higher Education (PBCOHE) does
for the community. Most of the users are intermediate individuals who only wish to be informed
and possibly join or assist in organization events and activities. These users have a motivation to
learn about PBCOHE and to potently join the organization. The remaining users are members and
board members of the organization who also have an intermediate expertise when it comes to
PBCOHE’s website and whose motivations are to read the newsletter, communicate with one
another, and to update information on the website.
P a g e | 9
Problem SpaceAs the site currently stands, pbcohe.org has an extensive list of problems. From diminished
functionality to its outdated layout, pbcohe.org is not attracting the students and high-level business
professionals it needs. Some of these problems include:
Data retrieval
o No clear and functional way to retrieve membership registration data
o Cannot collect membership fees online
o Paper-based membership data storage
Outdated mechanics
o Cross-platform browser issues (Internet Explorer)
o Dull, dark themed layout and background
o Slow
Newsletter integration
o Currently no support on the website for PDF viewing
Archiving of past events
o Multitude of old events for which the date has passed
o Pictures of old events not in order
Ineffective to users
o Information is not presented in a clear and concise way
o Not inviting
o Does not maximize screen space
We have come to the conclusion that the problems have arisen from lack of communication
coupled with the magnitude of the data and information received. The members of PBCOHE have
P a g e | 10
full-time schedules and duties that interfere with maintaining the product. These higher education
and business professionals do not always have the time to keep up with the demands of the
organization’s users. If editing and maintenance cannot be completed within a couple hours or even
a day, it will in turn find itself at the bottom of the stack. The client will own the site when we
complete it because the site now in place is owned by a third party.
With our proposed implementation, we plan to make sure the site is updated and give it a
brighter color and more inviting feel. We also want to make sure the site is functional on all if not,
most web browsers. In addition there will support for PDF viewing and downloading so that
members may receive up-to-date information about the organization. Lastly, we will our proposed
designs we plan to overcome the outdated navigation of the site and add in an archiving system for
past events.
P a g e | 11
Assumptions and ClaimsOur clients (Mrs. Thompson and Mrs. Daniels) expect nothing but the highest quality
product from the team and for the team to complete tasks in a timely fashion.
Initial Assumptions and claimsSome of the assumptions Mrs. Thompson made note of is the fact we are students in a class
tasked with working with PBCOHE to improve their website. She assumed we knew nothing about
the organization and what they do. She also assumed we had no prior web development experience.
We as a team assumed, our clients had no product to begin with and was looking for a
solution. We also assumed we would be working with the intentions of getting it reviewed by Mrs.
Thompson and Mrs. Daniels, not the entire PBCOHE organization. In addition, we assumed that
users are able to go on the site and see the upcoming events so that they may be a part of these
events. From the back end, we assumed that the client has a database of some sort so that there is a
record of members and event participants. Some of the initial claims were that users will easily like
the website, the learning curve of the product will be fast, and board members will be able to decide
the outcome of the product.
Reformulated Assumptions and claimsMany of these assumptions were wrong. Clients and the team alike have both reformulated
their assumptions. For example, the clients understand that we, the team, have experience in web
development, we now know a great deal about the Pennsylvania Black Conference on Higher
Education (PBCOHE) organization, and we are committed to building an excellent information
system. Some reformulated claims includes board members giving direction to the product
P a g e | 12
development monitoring user involvement, and recommending resources in addition to providing
instruction on product maintenance.
P a g e | 13
InspirationInteractive tools have helped NelsonsNaturalWorld.com make people aware of their health
needs with the features of a pregnancy nutrition quiz designed to give pregnant women nutrition
recommendations, and a comfort-eating quiz, allowing patients to track their eating habits (Nelsons
boosts website with interactive tools, 2012). The American Nurses Foundation launched a website
with an e-learning tool so that nurses can treat, evaluate, and refer people with post-traumatic stress
disorder (American nurses foundation launches E-tools interactive website to aid nurses in
providing PTSC care, 2014). The Informed Meetings Exchange (INMEX) has used interactive tools
to serve subscribers through interactive features and model reservation agreements (INMEX re-
launches website with new tools and interactive features for meeting professionals, 2006).
MotivationThe team’s motivation is partly due to the unsatisfactory status of the current product. In its
current state, the site is ineffective and does more harm and causes confusion than as an extension
of the organization. We believe we can bring a new take or look to PBCOHE’s problem. Being
college students ourselves, we have each been users the organization is targeting. We can give
insight and experience to what our like-minded peers would like to see and interact with.
Project PlanSemester project Revision and improvement
dates
Due date - Deadline
P a g e | 14
Phase 0 - Problem Space September 23-24 September 25
Team Meeting September 30
Client Meeting Week of October 1
Team Meeting Week of October 15
Phase 1 - Requirements
Analysis
October 20-22 October 23
Team Meeting October 27
Phase 2 - Design Alternatives October 27-29 October 30
Client Meeting Week of November 3
Team Meeting November 11 & 13
Client Meeting (If Needed) Week of November 18
Phase 3 - System Prototype November 17-19 November 20
Client Meeting Week of December 1
Team Meeting December 2
Phase 4 - Evaluation December 1-3 December 4
Team Meeting December 9
Client Meeting Week of December 8
P a g e | 15
Phase 5 - Project Presentation December 8-10 December 11
Team Meeting December 11
Client Meeting Week of December 15
Team Roles and Task AssignmentsNate Franklyn - Project Leader, Technical Writer, Designer
Project Leader: Assigned with making sure team stays on track and in line with set
deadlines. Communicates effectively with the client and team, making sure everyone is on
the same page. Organizes meetings, notes, and artifacts to present in a compelling
informative way. Assist all members of the team with applicable tasks, filling any gaps
along the way.
Technical Writer: Tasked with communicating design plans effectively and clearly to
everyone involved in the project. Reviews all documentation to see if it meets the client’s
specifications. Understands and educates the team on requirements presented from clients as
well as submitting documentation to third party writing lab for corrections.
Designer: Processes client requirements and vision into a workable solution that can be
implemented by the team. Assigned the duty of following the eighty - five guaranteed and
fifteen percent “Icing on the cake” rule. Also must take into account everyone’s skill set.
Tyesha Day - Tester, User Interface Specialist
P a g e | 16
Tester: Analyzes the requirements from the client, creates test cases, executes the test cases,
evaluates the results, and documents the problems found.
User Interface Specialist: Conducts tests of interfaces to make sure they are efficient and
attractive. Evaluates user interface to make sure the proposed prototypes will be received
well with targeted users.
Kneil Lindo - Systems Analyst, Programmer
Systems Analyst: Specializing in analyzing, designing, and implementing data and
information systems. Involves software development and making sure the functionality of
site is doing what it is intended to do.
Programmer: Writer of the code for the computer software. Pieces together ideas and
thoughts composed by the designer, team, and client to create team solution. Works with
designer to determine what can and cannot be done given team skill set.
ReferencesAmerican nurses foundation launches E-tools interactive website to aid nurses in providing PTSC care.
(2014). Retrieved from New Mexico Nurse: http://search.proquest.com/docview/1562156460?accountid=13158
INMEX re-launches website with new tools and interactive features for meeting professionals. (2006). Retrieved from Business Wire: http://search.proquest.com/docview/445138448?accountid=13158
Nelsons boosts website with interactive tools. (2012). Retrieved from Chemist & Druggist: http://search.proquest.com/docview/1010454790?accountid=13158
PBCOHE 44th Annual Conference. (n.d.). Retrieved September 22, 2014, from http://www.pbcohe.org/index.php?option=com_content&task=view&id=3&Itemid=34
P a g e | 17
PBCOHE 44th Annual Conference. (n.d.). Retrieved September 23, 2014, from http://www.pbcohe.org/index.php?option=com_content&task=view&id=4&Itemid=35
PHASE 1: REQUIRMENTS GATHERING AND ANALYSIS User Profiles
PBCOHE has five main stakeholder user groups: Administration of the system and the
organization, members of PBCOHE, Inquiring business professionals, interested sponsors, and
lastly inquiring students who are involved. These users have an age range of about eighteen years of
age to sixty and up. They’re very diverse sets of people whose needs need to be catered to. The
computer skills and internet skills cover the entire spectrum from novice to expert. Their key tasks
P a g e | 18
differ from each profile, since each one has different stake in the intended system. Here is a
breakdown of the users given in various profile formats:
Administrators of the System
Late 30’s & up professional individuals
Work in numerous fields and area of expertise. Great number of Higher Education leaders
and officials, who are at the heart of the organization. Able to do most operations and
activities accompanied by support.
Computer skills and internet skills are between the range of novice and intermediate level.
There are also handfuls of expert leveled individuals that may or may not use the system.
Tasks
o Managing the system
Controlling and maintaining optimal efficiency of the system and data for
continued use.
o Data gathering
Collecting data that will beneficial in decision making for the organization as
a whole.
Understanding their users and planning actions accordingly
o Posting, updating, and creating new content
Communicating events, opportunities, work to entire user base.
Becoming a prominent resource for Professional business men & women to
turn to.
o Collecting membership
P a g e | 19
Collect member dues to provide more opportunities.
o Troubleshooting
Fix pertinent issues affecting user experience and overall integrity of the
system.
o Teaching and educating users about the system
Passing knowledge on how to efficiently use the system for a better
experience.
o Communicating with users
Learning about users about their wants and needs to better assist them.
Members
Late 20’s & up business professionals
Members are individuals who support and back the PBCOHE organization. These users
come from all different fields and area of expertise. They are main user group actively
sought out by the organization and the most capable of all the user groups.
Computer skills and internet skills are in the novice to intermediate range. Again with
handfuls of expert leveled individuals
Tasks
o Presenting content to be posted to the system
Creating content that can then be shared to other users.
o Weighing in on key member issues
Helping to influence PBCOHE key decisions and direction.
o Paying member dues
Providing funds to the organization.
P a g e | 20
o Accessing information of use
Using the system as resource to better benefit their interests, and staying up
to date.
o Registering for Conferences
Using professional career building conferences to better themselves.
Sponsors
Could fall into any age range except under 20
Sponsors provide direction, expertise, and or monetary funds in backing of PBCOHE. Very
diverse set of users comprised of many highly educated, highly driven professionals.
Sponsors are capable of a great deal of actions, it’s hard to accurately subjugate sponsors to
one category.
Computer skills and internet skills are generally in the intermediate to expert level.
Tasks
o Inquiring information about PBCOHE from the system
Understanding and becoming involved with that PBCOHE does as an
organization
o Contacting administration or members of PBCOHE
Reaching important leaders for added information or clarification
o Requesting or filling out registration for Sponsorship
To become a part of the organization’s mission and vision
o Research
P a g e | 21
Learn more about PBCOHE’s intended focus and ways user can be beneficial
to them
o Donating
Showing support of the organization.
Inquiring Business Professionals
Late 20’s and up
Users in this profile are fresh into their fields and are looking to network in an effort to
better themselves. Also a key user group PBCOHE is trying to market to, these users are
highly educated and their capabilities are unparalleled
Computer skills & internet skills are usually in the intermediate to expert level, but there are
also novices
Tasks
o Gaining information from the system
o Joining the organization
Becoming a member of an organization comprised of highly educated
respected professionals from all walks of life
o Registering for events
Attending an event to increase their opportunities and skills.
o Downloading key pieces for review
Taking PBCOHE documentation for use on the go or later.
o Networking with member of the organization
Get to know the professionals in their field and receive guidance.
P a g e | 22
Inquiring Students
Between the ages of 18 - late 20’s
Student user are not really a main sought after user group but they are an audience PBCOHE
must cater to. These users are the incoming business professionals that with one day, may or
may not be, recruited by the organization. Their capabilities are endless, but are limited to
begin with. This because they malleable and moldable at this stage in their lives. But soon
will be dominant forces in the business world.
Computer skills are usually nice to intermediate varying slightly
Internet skill are more in expert range with a slight variation in the intermediate spectrum.
Due to the fact these users were born around in the internet age.
Tasks
o Communicating with Members
Reaching out and networking with members for guidance
o Registering for events
Attending Conferences to better themselves and gain a feel for the
organization
o Research
Learning more about PBCOHE and its role in providing underrepresented
professionals opportunities.
P a g e | 23
Personas
P a g e | 24
P a g e | 25
Functional RequirementsPBCOHE’s system and website has to meet or exceed the requirement of the users, their
needs and any future needs that may arise. The system will be reliable, the system must not be
plagued with errors or outdated materials, the system must also adaptable. Data collected in the
system must not be compromised. These are all key aspects of a functional system dependable and
reliable.
When administrators from the PBCOHE require active member list and key data concerning
the organization, the system must retrieve that efficiently and effectively. If this is not honored, the
system will become slow and more of a liability than business tool. The system must be fully
integrated with PayPal as a means of collecting transactions and donations. This is in effort to
transfer the liability and security of payment/financial transactions with a well-known trusted
source. So administrators and members can focus on strengthening and organizing PBCOHE.
The system has to convey the interest and issues of the Pennsylvania Black Conference on
Higher Education effectively and efficiently. This includes all information pertaining to events,
conferences, career builders, etc. The system must allow a way to capture registration information
for administrative processing. A members-only section the site must be created to honor those
involved with organization and promote communication within the organization. Failure to do will
result in miscommunication issues and the website remaining at its current state.
Non - Functional Requirements The system has to be aesthetically pleasing, vibrant, and easy on the eyes of the user. The
current system is very dark and lacks overall appeal other than a quick look. The system must retain
the user’s interest and feed it. Without taking this into account the organization membership will
suffer. Another non-functional requirement deals with adaptability of the system. The system must
P a g e | 26
be able to adapt to more or less all the changes or modifications PBCOHE requires of it. So the
system can remain an effective tool for the organization. The system should have an easy learning
curve because users and administrators cannot use a system that has a steep learning curve for
simple operations. Reference to help materials or suggestions would be most beneficial. The system
should provide troubleshooting options for members and administrators to help keep the flow of the
system. These options can include a general frequently asked questions document, support system,
issue reporting, etc.
P a g e | 27
Data RequirementsData will be collected every time members log in. From signing up for events, and
processing any type of transaction, to leaving a comment. Also when it comes to the actual data
and information, the website should update several times a day to ensure that the information on the
Pennsylvania Black Conference of Higher Education (PBCOHE) site is correct at all times. As for
privacy, the information is collected from users only to identify users as in conjunction with the
organization. When dealing with the efficiency of the data we want to make sure it is easily
editable, and reliable. The data should be safe when a user enters their information. Those with
access to administrative data will be able to view all content and have access to all information.
P a g e | 28
Context of Use Requirements
Social Environment The social environment for this organization is the one that promotes collaboration,
multiple connections to interface recognizing individual users and their contributions.
Data will be shared through admin and users. General data regarding or fit for the
organization will be reviewed and shared with the public. (I.e. membership growth,
member actions, etc.)
Collaboration has to be asynchronous and adaptive to all members, facilitated by
member login.
Interface must reflect changes and added data committed to be reviewed or presented
on the site.
Organizational Requirements System will use a level of tier system for an organizational set up, as the following:
o Admin
o Members-board
o Members-general
o Sponsors
o Business professional
o Inquiring students.
This system needs to be able to bridge the gap and communicate ideas efficiently to
other members.
Data has to be easily accessible so that other administrator board members can still be
connected and not be out of the loop.
P a g e | 29
Technical Requirements A system like this needs to be cross platform, being able to easily access website and
data from different internet browsers.
System also has to be compatible with multiple operation systems and the major four or
five web browsers.
System Documents and data should be easy to intermediate, and have transferable
portable storage.
P a g e | 30
Task AnalysisPBCOHE main focus is to provide programs and services which help ensure that the post-
secondary educational needs and aspirations of African Americans in particular are met, and to
work in concert with members of other underrepresented groups in the Commonwealth. With that
being said, our task is to help provide better web present to the organization partly by updating
website and social media aspects of organization.
Task: Goal:
-Update content on site -Information is up to date
-Update graphics on site -Making it more visually appealing
-Get admin control of site to appropriate admin -Have it more accessible in the right hands
The task environment is a shared space where ideas and interests can flourish as well as
networking for business professionals of all ages. Being an interactive site that appeals to all
business professionals, the system has to be professional and responsive. Business professionals are
always on the go and only have time for quick edit or comments before they are off to another task.
The task environment has to account for that; the most beneficial solution to this is using a web or
internet based system that any user can have access to anytime or anyplace. PBCOHE also needs
one that customizable to their needs, administrative controls for higher ranking members.
P a g e | 31
HTA Diagram
P a g e | 32
Data GatheringThe most effective method we used when it came to data gathering was interviewing and
having our client walk us through the site. We also ran comparisons of the way users interacted
with nobcche.org versus interactions with pbcohe.com. Our clients conveyed their issues and
requirements in each meeting as well as pointing out poignant issues with their current system.
Notes were recorded and reviewed after meeting as well as revisited several times. In the future, we
may invoke focus groups and questionnaires to poll the various user groups and the user experience,
more towards prototype and implementation phase. Stakeholders can attest that data gathered must
be clean and accurate for decisive decision making of the organization.
For the embedded design, the best method would be the use of observation and interviews.
We also noticed the emotions expressed on one subject versus another and gave us insight on what
was more important and what was more concerning. We also noticed the reactions of users to key
elements of the system. This was valuable information for understanding the usability of the
system.
P a g e | 33
Usability goalsUsability Goals
Standards that assure that the interface is easy to learn for users.
Effectiveness The completeness and accuracy with which users achieve specified goals. It is determined by looking at whether the user’s goals were met successfully and whether all work is correct. Is the site effective enough to where in this case spread awareness and generate donation?
Efficiency The speed (with accuracy) in which users can complete the tasks for which they use the product. Once users have learned the design, how quickly can they perform tasks? This is very important, if the end users have trouble navigating through a site then what is the point of going on the site?
Safe to use Involves protecting the user from dangerous conditions and undesirable situations. Anything that would have the potential to make the user become uncomfortable when going through the contents on site is unacceptable. It’s important to build a sense of trust between you and users.
Utility Refers to the extent to which the product provides the right kind of functionality so that users can do what they need or want to do.
Learnability How easy is it for users to accomplish basic tasks the first time they encounter the design? The user should be able to quickly become familiar with the site on first encounter and quickly be able to learn the ins and outs out site.
Memorability How easy a product can be remembered how to use, once learned.
User Experience GoalsUser
Experience Goals
How a user feels about a system when using it.
Motivating The site should impel a user to join the organization, become a sponsor, or donate.
Rewarding The interface should make a user feel as if they are valued when donating, becoming a member, or becoming a sponsor to the organization.
P a g e | 34
Satisfying The interface should meet the expectations of the users by providing background information on the organization so that users can know what are they donating to and why are they are signing up to become a member or sponsor.
P a g e | 35
PHASE 2: DESIGN ALTERNATIVESProject Description
The project set before us was to design and or update the Pennsylvania Black Conference on
Higher Education (PBCOHE) website and overall back-end system. PBCOHE’s current system is
plagued with errors and does not accurately represent them. This project is supposed to be
transposed on to the World Wide Web to be shown and shared with the world. It will be required to
accurately depict and communicate the wishes and ideas of the Pennsylvania Black Conference on
Higher Education. As well as support PBCOHE in all their tasks needed to assist their user/member
base. Lastly the system will shall be constructed as a tool and a resource to extend PBCOHE’s
reach/ influence in giving “Underrepresented professionals and students a voice in matters of higher
education.” (“Mission Statement”, 2014)
Key Requirements The proposed system for PBCOHE has several key requirements. These requirements are
split into two categories: Functional and Nonfunctional requirements. Functional requirements are
defined as the core functions of what a system should do. They are also the main focus of the
system and requirements activities. They encompass all the mandatory conditions and specifications
of the system in order for the system to be deemed efficient and operational. Nonfunctional
requirements are all the constraints on the system and development that are imposed over the course
system. These may include time, memory size, budget, resources available, etc.
P a g e | 36
Functional Requirements PBCOHE is coming from an outdated stagnate web interface. Due to the fact that the
administration has regular careers and other obligations; attention to the website and system is on a
volunteer basis. With this in mind, the system is required to be reliable and adaptable to multiple
users and their computer/internet skill levels.
The system must be responsive as well as efficient. Data collected from the system must be
stored and shared securely. The system must account for the future needs of the organization as it
grows its membership. Retrieval of data pertinent to PBCOHE administration and board members
must be available easy and efficiently. In addition, the system must be fully integrated will PayPal
as a means of collecting transaction and donations. Also there must be integration of a PDF file
viewer or a document viewer of some sort to showcase PBCOHE’s newsletter publication. In
regards to conferences, the system must allow a way to capture registration information for
administrative processing.
Lastly, the system must include a member’s only section to honor those involved with the
organization and promote communication among the organization’s members. Also the system must
have a section devoted to sponsors and those who wish to donate to the organization.
Non-Functional Requirements PBCOHE’s new system has to be aesthetically pleasing, vibrant and “easy on the eyes” of
the user. Coming from a very dark and lackluster interface, the new interface needs to attract and
entertain the user. The system must retain the user’s interest and feed it. The system must have an
easy learning curve, so that PBCOHE administration and new users can adapt to it. The system
must remain an effective tool for the organization and its members.
P a g e | 37
A core requirement of the system is the fact that, the system must convey the interests and issues of
the Pennsylvania Black Conference on Higher Education. This includes all information pertaining
to events, conferences, career builders, etc. There should be some functionality that identifies media
coming from PBCOHE and its members. Furthermore, the system should provide troubleshooting
options for members and administrators of the system to help keep the flow of the system. These
options can include a general Frequently Asked Questions (FAQ) document, support system, issue
reporting, etc.
P a g e | 38
Design Space Our team went through several design alternatives. They ranged from different platforms to
limitations on usefulness of the system. One alternative was the use of Drupal and its enterprise
business software package. Having an array of key features and support Drupal looked like a likely
choice, but installing it on a key stationary server was counterproductive on our end goals and user
requirements. After sorting through unfit design alternatives, we ended up selecting: WordPress,
Weebly, and a basic drawing board flow chart design.
Each design made has a unique attribute making it more beneficial for the user than the
other. Our design using Weebly is better inclined for the PBCOHE organization and is easier for
one to manipulate it. It’s also very user friendly and easy to remember how to use. The design we
made using WordPress is better inclined for customization. It’s a better fit for a user to have the
freedom to design a layout exactly the way they want, but at the same time it is harder to
manipulate. Also being pretty code intensive, the users may have a problem adapting well. The last
layout was design using Visio. Visio makes it easier for the users to get a clear concise
understanding of organization of the website, but is limited when it comes to customization.
Given the time constraint, there is only so much we can do given the key requirements we
were asked to meet. So a tradeoff we had to make was which design would be more labor intensive
to achieve the same goal. Another tradeoff was ease of use and the learning curve associated with
each design. We have to turn the end product over to a group of PBCOHE professionals so that they
may decide if they want to go ahead with the implementation. Our main duty is to go with a system
that best appeals to their organization. We want to create a website that instills confidence,
whenever a stakeholder is using the system.
P a g e | 39
Design Assessment
Usability Goals The guidelines and measurement of how effective, efficient, easy to use,
memorable, etc. a particular tool or system is.
Effectiveness The completeness and accuracy that a site can do what it was intended to do.
Efficiency The speed (with accuracy) in which users can complete tasks for which they use the product. The interface must simplify process of users to understand, and find out new and exciting things about the organization.
Safe to use Involves protecting the user from dangerous conditions and undesirable situations. Anything that would have the potential to make the user become uncomfortable when going through the contents on site is unacceptable. It’s important to build a sense of trust between you and users.
Utility The interface should provide appropriate set of functions that will enable users to carry out all their tasks in the way they want to do them.
Learnability The user should be able to accomplish basic tasks the first time they encounter the interface, become familiar with the site, and be able to learn the ins and outs of the site.
Memorability The interface should be easy to remember once learned.
Usability goals are the guidelines and measurement of how effective, efficient, easy to use, memorable, etc. a particular tool or system is.
P a g e | 40
User Experience Goals
The overall look and feel of the website pertaining to the User
Motivating The site should impel a user to join the organization, become a sponsor, or donate.
Rewarding The interface should make a user feel as if they are valued when donating, becoming a member, or becoming a sponsor to the organization.
Satisfying The interface should meet the expectations of the users by providing background information on the organization so that users can know what are they donating to and why are they are signing up to become a member or sponsor.
Comparison of the Prototypes against the Criteria Prototype 1
(WordPress) Prototype 2
(Weebly) Prototype 3 (Visio
Studio)
Effectiveness X X
Efficiency X X
Safe to use X X X
Utility X X
Learnability X X X
Memorability X X
Motivating X
Rewarding X X
Satisfying X X
P a g e | 41
Summary/Reflection
As mentioned, the current PBCOHE website was very out of date and not very visually
appealing. So from the start we knew we had to change the colors and make it seem more inviting
and friendly. For one of our designs we wanted to liven the site up with a white background to make
P a g e | 42
it seem alive instead of a gloomy dark black color. With changing the background color it also
makes it easier to read certain texts and spot out things on site.
We then noticed on the current website it had old information and even the relevant
information wasn’t noticeable upon first encounter. So on one of our prototypes we decided to
reorganize where the info is placed on the site; making certain info becoming an attention grabber
upon first look, with that we can get rid of all unimportant and old information.
All these changes were possible to accomplish and necessary for the website. Client did
mention those were important parts of the site that needed to be altered so we definitely wanted to
do. And with our changes of course we had to take into account the certain usability goals so the
users have an easy time going through the site. Making changes to the structure and color schemes
hopefully makes it more effective to the user so it gives a better understand of what the company is
all about. Along with effective we try to include all usability goal in each development in our design
layout.
Teamwork Team TNK consists of three members: Tyesha Day, Nate Franklyn, and Kneil Lindo. We
are well-versed in a different area of IST and Design. To achieve a complete and utter
understanding of phase 2, we reviewed and brainstormed solutions to each of the objectives present
in the problem document. We decided to employ a divide and conquer strategy when it came to
P a g e | 43
understanding each objective and then educating the other group members about it. In regards to the
designing of the design alternatives. We all agreed to sit down at the library and collectively design
the alternatives together. Each team member had some influence in regard to how the look shape
and feel of the design. Having three different perspectives on prototype allowed us to see the
functionality from all angles.
Prototype Presentation
Prototype One - WordPress platform Codename “#1 Draft Pick” WordPress was our overall first pick in regards to a solution for PBCOHE’s problem. The
WordPress platform has the tools needed to transform the current state of PBCOHE’s system. With
P a g e | 44
the ability to pick multiple themes and customize the raw html code for specific pages, one can
really transform a site. The dashboard is a clean and crisp interface allowing new content additions
and customizations easy and on the fly. The only drawback is the fact that WordPress can be code
heavy and intensive for new users.
P a g e | 45
P a g e | 46
P a g e | 47
Prototype Two - Weebly platform Codename “Training Wheels” Our basis for this design was usability in regards to the intended end-users. We wanted go
with something that was easy to maintain and had an even easier interface. Weebly was our choice
because of its drag and drop features for adding new content and new functionality. More of the
built in themes were not code heavy, but gave a vibrant look. The only downside to this option was
the lack of customizability from platform presets.
P a g e | 48
P a g e | 49
P a g e | 50
Prototype Three - Codename “Drawing board” Visio studio made it easy to get a first look overview of what we have to deal with and what
we want to work with. It was almost the blueprint of a basic design layout so we can see what we
can manipulate and what we had to work with. This as well had drag and drop features so it was
easy to move designs around and get a feel of how u want a design layout to look.
P a g e | 51
PHASE 3: SYSTEM PROTOTYPE AND EVALUATION PLANProject Description
The PBCOHE website revival project consists of updating the current web space associated
with the Pennsylvania Black Conference on Higher Education. The proposed update encompasses
establishing control of the intended system, redesigning the homepage and entire front-end layout
of current system, integration of PayPal and conference registration system, organizational access
levels for members, etc. The intended users of the new system include: The PBCOHE
administration, the PBCOHE Organization Members, Inquiring Professionals, and Inquiring
Students. We designed the proposed system and chose a particular interface with a user friendly
design in mind. By using Weebly or WordPress, creative control is in the hand of who or whom
holds the password. In addition, accessibility is everywhere a user has web/internet access.
P a g e | 52
Requirements Summary The PBCOHE system requires several key requirements. These include functional and
nonfunctional requirements. Functional requirements are defined as the expectations of what the
proposed design or system must do. Non Functional requirements on the other hand are defined
as the expectations of what the system should do (i.e. memory size, visual aspects, how to judge
the system, etc.)
Functional As stated in the Phase Two document, the proposed system must be readily available, easy
to use, and efficient. The system must be able to be used as a tool and an extension of
PBCOHE and the organization’s views. In order to accomplish this the system must be able
reliable and adaptable to multiple users. The system must also be fully integrated with PayPal as
a means of collecting donations, registration fees, and membership dues.
In addition to these requirements, the proposed system must be able capture conference
registration data, display/make available the organization's newsletter to it members, and
incorporate a definitive member access section.
Non-Functional The proposed system must be vibrant and aesthetically pleasing. Also the system must
provide or have troubleshooting options for members and administrators to keep the flow of
information. The system must have an easy learning curve for members of the organization to
use the system better and be taught with relative easy. Lastly, the system must convey the
interests of the Pennsylvania Black Conference on Higher Education.
P a g e | 53
Design Summary Each design made has a unique attribute making it more beneficial for the user than the
other. Our design using Weebly is better inclined for the PBCOHE organization and is easier for
one to manipulate it. It’s also very user friendly and easy to remember how to use. Our basis for
this design was usability in regards to the intended end-users. We wanted go with something that
was easy to maintain and had an even easier interface. Because of its drag and drop features for
adding new content and new functionality, it makes it easier for user to edit and make changes.
As far as the actual design of the interface goes, we started with making the title of the
organization clearly at the top in the header. And since we changed the background color from
black to white, we made the font color of the organization’s name black so colors are now
contrasted and it is easier to notice. Alongside of the name, organization’s logo is clear and
visible. Also in the border, the navigation bar is found above the name of organization. With it
being at the very top, there won’t be a mistake looking for navigation. Since it is known to be at
the top in the border we want to keep it consistent so users have an easier time going through the
site. In the middle of the page, we put a large image representing the Pennsylvania Black
Conference on Higher Education. When you first visit the page, it’ll catch your eye and makes
you wonder what they’re about. Then for the visitors convenience there is a quick mission
statement right underneath so the viewer has a better understanding on what this organization is
about. Instead of having the home-page being congested with words, we have a video ready to be
viewed. This is so the viewer can feel as if they are a part of community and we give them
something they can be enlightened about.
The design we decided to implement has a crisp, clean look to it. It’s looks inviting and
looks much more “safer” to use, due to the change from black to white background. It’s not
P a g e | 54
cluttered upon first look and it doesn’t give off an overwhelming experience. In the end the
system design is easy to use, and efficient. Also has an easy learning curve and the layout is neat
and organized.
P a g e | 55
Prototypes The Weebly platform was selected by our clients because of the ease of its drag and drop
features when adding new content to the website. The reason why our group chose to create a
prototype with Weebly is because this platform is not time-consuming. Most of the chairmen &
chairwomen in PBCOHE’s organization are volunteers which means they have other obligations to
tend to as well. Our plan for the prototype is to make the website bright and easy to navigate by
displaying five simple navigation buttons. The home screen instantly captures user’s attention so
that viewers can know what PBCOHE is about and their mission statement. The members tab is
exclusively for members of PBCOHE to log-in and have exclusive access to things that a visitor
would not have access to. The members tab also displays the newsletter for the month for members
to view. The events and donations tab is where upcoming events are located and where people can
donate money to the organization and pay for conferences online. The contact tab is where users
can send comments to the organization.
P a g e | 56
Screenshot 1
Screenshot 2
P a g e | 57
Screenshot 3
Screenshot 4
P a g e | 58
Screenshot 5
Screenshot 6
P a g e | 59
Evaluation plan
Our high level goals for this project encompass all conveyed requirements as expressed
from our clients Mrs. Barbara Thompson and Mrs. Cynthia Daniels. Spanning a wide range of
areas and particular to each issue, these goals are meant to evaluate the intended system and provide
feedback.
Goals • To provide a reliable well-accepted system that PBCOHE can effectively use.
• Usability of the system and learning curve are in the range of meeting PBCOHE needs.
• Create member connections and better flow of information.
• Bridging the gap between PBCOHE and updating content.
• Create a better and efficient way for collaboration of between organization members and site
administrators.
• To gather data in an easy interface that is less complicated and more organized than
PBCOHE’s current system.
Questions that address these goals • What features of the system best helped you complete your intended task?
• How well you were able grasp the controls of the system?
• Was there anything that hindered your learning progress?
• Do you feel confident in using the proposed system again?
P a g e | 60
• Using the system were able to connect with other members and build connections?
• What would you most attribute to the success of learning and using the proposed system?
• How long did it take for you to update content?
• Were you able to complete a PayPal transaction and or register for an event?
• How might you improve this intended system
Methods of Evaluation To evaluate the effectiveness of our proposed design we will use a combination of methods
in our study. Our first method will be the use of questionnaires to collect data on the effectiveness
of the site and its features. Users will be presented with several questions to reflect about their
experience while using the proposed system. These questions will gage how useful and how well
the system was able to address the key requirements set forth by the stakeholders. Users will be
required to answer all the questions to the best of their knowledge after they have had ample time to
experience the proposed system design.
Our second method of evaluation will be the use of usability lab. Since our team does not
have access to an already established lab, will do our best to create a mock up one. Using a
combination of both a controlled environment and natural environment; we will conduct these
evaluations in the user’s natural location/space, (i.e. Home, Work, Library, quiet space, etc.). We
will accomplish this by direct observations and statistical analysis from the website monitoring
data. Also, the use of a stopwatch and record keeping will be present throughout the observation
process so the design team can see time spent on specific areas of the system. We predict this
P a g e | 61
process should take no more than 45 minutes to 1 hour for each client as well randomly anonymous
users.
Our last method of evaluation will be the use of field studies. Over the coming weeks we
will take survey of random users and see how they react with system out in the field. This method
helps increase the diversity of the study and gathers a wide range of user experience different from
the last. PBCOHE has many members from all walks of life and professions, so we have to equally
represent them and their needs when developing a final system prototype/solution. Aided by direct
observation, we will be looking for areas lacking great user experience and usability.
Practical Issues As with any evaluation plan, we must account for any practical issues we may encounter
while executing said evaluation plan. Some these issues include:
• Time constraints - The evaluation phase of this entire project is only for a couple weeks. In
order to gain the greatest varying range of evaluation data, one must evaluate the system for
months let alone mere weeks. Our team is on a thinning timeline with the academic semester
near its end.
• Mobility and Reaching Target Random Groups - We cannot reach everyone we need to poll
and evaluate the system perfectly. So while using the data we do gather, the team will have
to make design choices and revisions on that.
• Human Error and Unaccounted for Error - Error is present in every study. Human Error is
one those variables that cannot be subjected out all the time. So the data may not be 100
percent correct but will be in the 90th percentage range.
P a g e | 62
• System maintenance and Downtime - Since the proposed system is web-based, the overall
website and back-end is hosted on a company server. Routine maintenance is required from
time to time and may interfere with conduction of the direct observation and surveys.
Ethical Issues The evaluation plan set forth and constructed has little or none ethical constraints. But in the
effort to plan if some arise, they might include:
• The Sharing of Personal Data - The evaluation plan accounts for anonymity when
questioning or observing random users.
• Keeping or Storing Observation Data - Only used for evaluation purposes, data collected
will used to better the proposed system and be used as constructive criticism.
• Gaining Consent or Willingness to Volunteer - Forcing participation of study out of a user
will hold no bound in this study. Protection of user rights shall be accounted for
• Privacy - If the user requests to evaluate the system alone or would not like to be
represented in the study with us; the design team, must honor that.
• Harm - No harm shall come to the users, the participants, the researchers or the observers.
• Deception - While conducting this study, users and participants shall have full knowledge of
what this study wishes to accomplish, the process it will undergo to reach completion,
variables associated with this study, and any or all information required to make an
informed consent.
P a g e | 63
Summary/Reflection
As mentioned, the old PBCOHE website was very out of date and not very visually
appealing. So from the start we knew we had to change the colors and make it seem more inviting
and friendly. For one of our designs we wanted to liven the site up with a white background to
make it seem alive instead of a gloomy dark black color. With changing the background color it
also makes it easier to read certain texts and spot out things on site.
Having different set of prototypes helped us identify what layout and what type of
organization was best suited for this organization. Testing out which layout would be better
appealing from the users end and at the same time making it easier for admins to make changes.
We were basically finding the median for both.
Having picked our layout of course we had to take into account the certain usability goals so
the users have an easy time going through the site. Making changes to the structure and color
schemes hopefully makes it more effective to the user so it gives a better understand of what the
company is all about. Along with effective we try to include all usability goal in each development
in our design layout.
P a g e | 64
PHASE 4: EVALUATIONOverview
The basis of this phase is the effort to evaluate and improve the intended proposed system.
This is a report on how said evaluation plan was planned out, carried out, and review. Also the
findings and solutions that were brought out in result of this evaluation. This evaluation plan was
merely a way understand the system and build it better.
Description of Methods, tasks, and usersThere were two methods used exclusively in this evaluation plan: The Usability Lab/Think
Aloud and a Verbal questionnaire. A Usability Lab is the direct observation of a subject taking note
of their actions, emotions, and decisions taken while using the proposed system. A Think Aloud is
the verbalization of one’s actions while using the system and watching their reactions. Lastly, each
one of our team members got together and developed four to six questions to ask after the system
run-throughs were completed. The questions we asked were:
In regards to the general layout, was it aesthetically pleasing?
Were there any parts of the website dysfunctional or served no purpose?
Was the enough information on the members landing page or too much?
Would you visit the site again?
What were you first thoughts of the website?
How can we improve this design?
Which one would you rather visit the current site or this proposed one?
P a g e | 65
These questions were asked because they each hit on one of the user experience or usability
goals we employed earlier and throughout the entire semester project. They are a means of
understanding the user’s actions.
We also ask the users to complete certain tasks and we timed their process we choose these
takes because they best represented how the system meant to be used by users of various computer
levels. A list of the tasks are:
View each page
Click every button and link
Attempt to register with a conference
Download the Newsletter
Submit a contact request
Visit social media page via links (Top Right)
P a g e | 66
Design Rationale for Methods and MaterialsFor the evaluation methods we employed, we designed them to test a number of areas of the
system. We design them to also be easy for the user recall and answer. A series of yes and no
questions as well as open ended ones. We decided to with a Usability lab and Think Aloud so that
we could witness the system being used and its particular fall outs compared to the current website
set in place for the organization. We wanted the user to feel comfortable in their own natural
settings and give us honest answers.
We had a number of constraints and limitations on the materials we could use for the
evaluation. This was become of the overall time constraint and our overall ability. For example, we
could not record or videotape any of our subjects/user. This was because we would be able to get
the proper clearance to conduct such a practice from the University. So instead we took notes and
practiced direct observation. We weren't allow to identify any of our users/evaluators; and if we did
so it, it was mandatory that it was anonymous. This was in effort to protect both parties. We were
limited to the use of a stopwatch to time user interactions because it was the most viable means to
testing ease of use.
P a g e | 67
Summary of FindingsWe had a total of eight user/evaluators. These users spanned various ages from 18 - 60 and were
in various professions. We tried to choose a group of two users to represent each of PBCOHE’s
target stakeholders. We attempted to match each novice computer user with an expert leveled
computer user in our analysis. In our findings:
We found that more or less all the chosen evaluators found the new proposed design more
aesthetically pleasing than the current design
The average time to complete the Usability Lab test and Think aloud was 16 minutes and 14
seconds.
A great number of User’s first thoughts; when visiting the website, were: “It looks
professional”, “Clean”, “Organized”, etc.
We encountered during the evaluations that sometimes load times affected the way the
website flowed
There was a split decision whether or not there was too much or just the right amount of
content listed on the members landing page. Features like the Newsletter gave the page a
busy feel.
The Contact us page was a little lacking of content. But overall efficient.
Some of the content on the website had longer load times. We attributed to different
browsers and systems
A lot of the evaluators believed there should be some way of seeing where their membership
or donation monies are going to.
In an attempt to see if anonymous users could updated content from the backend interface.
We found out that more than half of the evaluators needed further instruction in order to
carry out some actions.
P a g e | 68
Discussion of ResultsAll of the usability and user experience goals were set to achieve the best experience for
stakeholders. When evaluating participants while they tested out our prototype, navigating through
the interface was simple for each person, but a couple of the participants stated that the load time
was a problem for them. When a participant clicked on the slideshow, it took a few minutes to load
the pictures and to function properly. Another problem that a participant identified was a button that
was not working accurately; this button lead the participant to an administration sign in page.
When asked about the visibility of the interface, we were told that the prototype was inviting,
pleasing, clean-cut, organized, vibrant, and professional for the most part. However the participants
felt that the newsletter should be place in another section to minimize the amount of information on
the page.
Design Implications From the feedback of the participants that evaluated our website, we discovered that we
have three issues with our interface. The first problem with the website is when a picture or link is
P a g e | 69
clicked, the response time is slow. Secondly, when the learn more button is clicked on the home
page, it leads to the administration sign in page. Finally, the last issue with the website is that the
members’ page displays too much information, both the slideshow and the newsletter is located on
this page.
ImprovementsFrom the feedback we received from the users testing out our website, we decided
P a g e | 70
To make change on numerous things. First being, making the newsletter and forums accessible to
non-members. So without membership access you cannot see it. This reduces a lot of cluster and
not as stress on the user’s eyes. Once you are a member, the newsletter will get its own separate
page for members to look through. Also we received comments mentioning that they would like the
pictures in our slideshow run automatically. Some were unaware there were more pictures available
to view, so if it ran automatically there wouldn’t be any risk of missing photos. One big issue also
was users not knowing who specifically to contact. Users were looking for a FAQ page so to speak.
They want to be able to email, or call directors of the organization, or if they have questions they
are able to contact directly. One improvement also made was not having so many things on the page
at once. We got comments saying content would appear “hidden” because they didn’t know there
was more info under our picture slides. It took up a lot of room it looked like that was the only thing
on the page. We now know we should condense certain things so mostly everything can fit on
screen looking more continuous. Last users wanted to clearly distinguish the events and donation.
We will address the issue by having them on separate pages and having a more descriptive
explanation of each entity we have listed. With this is seems more reliable and trustworthy for the
users. If we had more time we really wanted to get the member’s access parts running efficiently.
Our client were really fond of having a members sections only within the site.
CritiqueThere are a number of things we could have done differently. Even though we took a user-
centered design approach to the building of the website, we still kind of made some assumptions on
the overall ease of use. We can definitely fix that with instruction. With more resources our team
P a g e | 71
could have conducted a proper Usability Lab and registered all the different interactions our
evaluators had. We also wished we had more time, so that we may have been able to gather more
data and more views. Instead of having two evaluation methods, our team could have solely focused
on the Usability Lab. We wanted to get the best diversity of information and various viewpoints. A
tradeoff was that we may have stretched ourselves thin.