Professional Documents
Culture Documents
Requirements FlexSim
Requirements FlexSim
Paula Mora
PUID: 0035422359
4. Review steps in bibliometric analysis and share some images with brief
interpretation of results. Be sure to include at least three of the steps in bibliometric
analysis shown in lessons.
Bibliometric analysis steps:
1. After analyzing some topics, I was most interested on I found some articles and graphics
2. I chose the words ergonomics, flexsim and optimization
3. I used Scopus for my research
4. Based on the publication date I chose one of the newest publications
Link: https://www.scopus.com/record/display.uri?eid=2-s2.0-
85138836074&origin=resultslist&sort=plf-
f&src=s&st1=flexsim+AND+optimization+AND+ergonomics&sid=d7d909c0e2f867c8b578
f62a6b3cb8e2&sot=b&sdt=b&sl=54&s=TITLE-ABS-KEY
%28flexsim+AND+optimization+AND+ergonomics
%29&relpos=0&citeCnt=0&searchTerm=
5. Based on this article I will be able to dive into simulation and optimization at a safe
workplace
5. Tell about your experience in using the software and relate your experience to any
awareness you developed about recent literature. Briefly read and cite at least 3
articles or news-related items. Include in introduction or discussion.
Although it was challenging, using software is useful not only for the class or my major but to
use it in an industry. Here are some articles that explain the future of software in the industry.
Citations:
M. Jazayeri, "The education of a software engineer," Proceedings. 19th International
Conference on Automated Software Engineering, 2004., 2004, pp. xviii-xxvii, doi:
10.1109/ASE.2004.1342718.
Gail, C. & Notkin, D. “Software Reflexion Models: Bridging the Gap between Source and High-
Level Models”. University of Washington.
V. R. Basili, "Software development: a paradigm for the future," [1989] Proceedings of the
Thirteenth Annual International Computer Software & Applications Conference, 1989, pp. 471-
485, doi: 10.1109/CMPSAC.1989.65127.
9. Be sure to include meaningful captions for any tables and figures. Show an example
here.
The figures and tables on the report show important information. The results of this image, for
example, show the growth of research since the 2000´s when using the words: simulation,
ergonomics and optimization in nGarm.
10. Students should work in groups of 2 or 3. Students are allowed to work individually.
However, this is intended to be a group or team assignment. There are enough items
to complete, in addition to using the software, to justify cooperation.
Group of 3:
Jolee Hedman
Francisca Cevallos
Paula Mora
11. Students should declare their intention (who they will work with or that they plan to
work individually) in separate TopHat post.
We plan to work in a group of three to share knowledge about simulation and optimization in
ergonomics.
12. Students should refer back to experiences from video and use of software, including
image captures uploaded to HotSeat in draft and final report. It is fine to include
other images to help communicate about procedures and functions that students
used or thought were useful for engineering or education purposes.
We explained difficulties and challenges from the first experiences using the simulation
software. This was the photo I uploaded to Hot Seat. The video recordings in Brightspace were
helpful to look back and practice the use.
13. Be sure to check grammar and include image of grammar score in requirements doc
based on draft and revised report (before and after modification). More than one
version can be uploaded to draft report link in BrightSpace.
14. Check authenticity score based on draft report and revise if any sections are flagged
by similarity match. Students should include an image capture in requirements doc.
More than one version can be uploaded to draft report link in BrightSpace.
15. Upload draft report to BrightSpace in two weeks by end of day (Wednesday in two
weeks). Review similarity score (any scores above 25% will require separate written
justification when submitting final report). Students should be able to view their
percent match in BrightSpace.
16. All reports should have fully developed abstract, keywords, introduction,
procedures, results discussion and reference section. References should be
formatted in Chicago style. If another format is used, the format should remain
consistent and according to Springer (template) format.
We included all the sections and Chicago citation.
17. Individual students should complete one requirements document as part of the
process of compiling the report. The individual requirements document should be
uploaded to BrightSpace in separate link from report. It is recommended that teams
complete one requirements doc as a step toward preparing the final report, but the
team-based requirements doc will not be uploaded.
I will upload this document to Brightspace. I solved it individually.
18. All students should complete the peer evaluation and upload to BrightSpace link.
Separately, an image capture of some portion of completed peer evaluation should
be included in requirements doc.
19. Scoring for the report will be based proportionally on images in HotSeat and
TopHat discussion (FlexSim and report-related participation), the requirements doc
(submission in BrightSpace with 20 items filled in by screen capture or copy/pasted
text) and the graded (ranked) report. Though reports will have a team score, all
students will have an individual score based on their participation and completion
of each of these elements. The HotSeat posts and TopHat discussion related to
report will represent 20% of scoring. The requirements doc (individual) will
represent 30% of scoring and the report will count as 50% of scoring. So there will
be a team-based part of scoring (50%) and individual part (50%) of scoring.
HotSeat posts related to this topic will remain open through end of Friday. TopHat
discussion boards related to report will remain open through end of next week.
I submitted all the posts from Hot Seat and Top Hat. Final report due November 1st.
20. Report scoring will be based on written communication capturing coverage of the
elements of this requirements document. Emphasis and recognition will be given to
reports that capture the detailed functions used to complete participation, the
relationship with ergonomics and the report-style elements and meaningful
relationship to course text and existing literature. See examples in published
literature shown in lesson (eg. Sinchuk et al. 2020; Naidu et al. 2022; Roach and
Duffy, 2021; Anton and Duffy, 2022 or Sheikh and Duffy, 2022) for ideas about style
and breadth of coverage on elements overlapping with requirements doc. Full text
versions can be found via the ResearchGate or Google Scholar sites:
https://www.researchgate.net/profile/Vincent-Duffy-2/research or
https://scholar.google.com/citations?user=3ER3-UUAAAAJ&hl=en&oi=ao