diff --git a/README.md b/README.md index c63cbbfa79eb4a72ebdbcfb2a9cb472986b23163..d4b91c7668e69f3018a9aad6f4f6dae59faabcec 100644 --- a/README.md +++ b/README.md @@ -1,93 +1,52 @@ -# hci-2024-2-final - - - -## Getting started - -To make it easy for you to get started with GitLab, here's a list of recommended next steps. - -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! - -## Add your files - -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: - -``` -cd existing_repo -git remote add origin https://git.ajou.ac.kr/ekdusld/hci-2024-2-final.git -git branch -M main -git push -uf origin main -``` - -## Integrate with your tools - -- [ ] [Set up project integrations](https://git.ajou.ac.kr/ekdusld/hci-2024-2-final/-/settings/integrations) - -## Collaborate with your team - -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) - -## Test and Deploy - -Use the built-in continuous integration in GitLab. - -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) - -*** - -# Editing this README - -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template. - -## Suggestions for a good README - -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. - -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. +# iPhone 시계 App Reverse Design 프로젝트 + +## 개요 +본 프로젝트는 iPhone 시계 앱의 네 가지 주요 기능인 **세계 시계**, **알람**, **스톱워치**, **타이머**를 분석하고 역설계하여 App Reverse Design을 문서화하는 것을을 목표로 합니다. 이를 통해 사용자의 시간 관리와 관련된 여러 과제를 해결하는 효율적인 앱으로 개선할 수 있습니다. + +## 기능 분석 +### 1. **세계 시계 (World Clock)** +- 사용자가 여러 지역의 시간을 동시에 확인할 수 있는 기능. +- **문제점**: 다양한 시간대 추가 시 화면이 복잡해짐. + +### 2. **알람 (Alarm)** +- 설정한 시간에 알람을 울리는 기능. +- **문제점**: 수면 패턴 및 활동내역 기반 라이프 사이클 자동 추천 기능 부족. + +### 3. **스톱워치 (Stopwatch)** +- 시간 측정을 위한 기능. +- **문제점**: 멀티태스킹 지원 부족, 반복 측정 기능 부재. + +### 4. **타이머 (Timer)** +- 사용자가 설정한 시간 후 알림을 주는 기능. +- **문제점**: 다중 타이머 설정과 반복 타이머 기능 부족. + +## 설계 단계 + +### 1. **개념 설계 (Concept Design)** +- 사용자의 요구를 반영한 기능 분석과 대안 제시. +- **페르소나**: 21세 대학생 이다은을 기반으로 타이머, 알람, 스톱워치 기능 분석. +- **대안 제시**: + - 멀티 타이머 지원 + - 알람 자동 추천 기능 + - 타이머 반복 설정 기능 개선 + +### 2. **정보 설계 (Information Design)** +- 앱에서 필요한 데이터를 수집하고, 이를 구조화하여 효율적인 정보 흐름을 설계. +- **정보 구조**: 주요 기능별로 구분하고, 사용자가 쉽게 접근할 수 있도록 설계. + +### 3. **상호작용 설계 (Interaction Design)** +- 사용자의 행동에 따른 앱의 반응을 설계. +- **인터랙션 개선**: + - 알람 설정 시 직관적인 UI 제공 + - 타이머 사용 중 간편한 타이머 추가 및 삭제 + - 스톱워치에서 기록 기능 향상 + +## 목표 +- 사용자 경험을 개선하고, 직관적이고 효율적인 시간 관리 도구로 발전시킴. +- **기능 개선**: + - 멀티 타이머 지원 + - AI 기반 알람 추천 + +## 기술 스택 + +- **설계 툴**: Notion (문서화 및 프로젝트 관리)