This repository has been archived by the owner on May 5, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 108
GSoC 2015 Sanya Jain
Janice Niemeir edited this page Jan 25, 2018
·
1 revision
I am an undergraduate student pursuing B.E.(Hons.) Computer Science from Birla Institute of Technology & Science, Pilani, India.
I believe in taking new initiatives, venturing in diverse fields and learning from all the experiences and activities that I get engaged in. I like to set my priorities right to achieve my targets and give my best at whatever I do.
Greatly looking forward to a fruitful experience of learning, coding, skill acquisition, networking and community development this summer!
Github
Facebook
LinkedIn
Gmail
Abstract- A female empowerment educational app that allows young girls (12 to 14) to learn about reproductive health and self-esteem by navigating the life of their avatar. Through this project, I hope to implement features that would serve as better options for educating preadolescents who are at risk for pregnancy and spread of sexually transmitted infection(STI) due to lack of information about the associated risks and responsibilities.
Timeline - Before Mid-Term
Timeline - After Mid-Term
To Be Updated..
- Made a revised timeline in sync with the Android platform team
- Read up on iOS development and development environment setup, tested first on Virtual Machine and then eventually got a MacBook, got familiar with XCode and explored Objective-C and swift.
- Research on the pros and cons of Database keeping in view the curriculum for the game. Zeroed down on SQLite database which will be used commonly on both Android and iOS platforms to develop the game mechanics.
- Alternatives for database model explored keeping in view the entities and attributes according to the curriculum of the game.
- Unfamiliarity with the iOS platform.
- Issues while working on the VM.
- With the help of mentors and online resources, got a better grip for working on the iOS platform.
- Got a MacBook and explored XCode
- Some doubts regarding the development of database and the game mechanics.
- Arranged a google hangout with the entire PowerUp team for the same(Scheduled on June 2, 1 pm EST).
- No.
- Implementing the database on the proposed database model(after discussion with mentors and project managers).
- Documentation
- Testing, fixing bugs
On schedule.
- Made several drafts of the database schema design according to the game mechanics mentioned in the proposal.
- Had a Google Hangouts session with the entire team of PowerUp to understand the finer details of game mechanics and to clarify doubts about the development of Database.
- Developed a final design of database schema and attributes along with a sample conversation(for the game) and entity & class diagrams after the hangout session and feedback from mentors.
- The discussion about the database design was an iterative process and it took more than expected time to understand the intricacies of game mechanics. Hence, after discussion with mentors, changes were made in the design of database late into the week to accommodate all the specifications and assumptions.
- Discussion with mentors and project managers led to covnstructive feedback and helped us in refining the design of the database for the game.
- No.
- No.
- Implementing the database based on the final database model, documentation and removing errors.
- Behind schedule because the discussion about development of database according to the game mechanics got delayed, it was an iterative process
- We have drafted a revised timeline with milestones and deliverables to be achieved weekly.
- Worked on using SQLite database in the iOS app in Swift language
- Created the database using SQLite manager which is an add-on plugin of firefox. The sample conversation data was input into the database by importing CSV files.
- Used FMDB wrapper for using SQLite in iOS to access the database inside the app, wrote the code for querying an retrieving desired output
- Swift is the new programming language of iOS; there were issues in using SQLite with Swift and gaining access to the database.
- Yes.Discussion with mentors, help of online resources and the thread on systers wiki where I got inputs from other people working on iOS helped a lot!
- Basic implementation has been done. For feedback and iterations, a Google hangout session has been scheduled with the entire PowerUp team on 16 June 8 pm EST.
- No.
- Work on setting up the introductory screen.
- Make active links of buttons
- Setting up separate screens for “About” section
- On schedule
- Pushed the database implementation and screen navigation code to GitHub after forking repo,making changes, committing the code in the forked repo and submitting the pull request on systers/PowerUp.
- Worked on creation of the introduction screen from the mock-ups and images provided by the project-managers. The start screen for the game is now ready.
- Worked on the creation of a clickable map where users will be able to click on various destinations on the map.
- Made active links for some buttons, the screens of which are up and ready.
- Not having prior experience of Version Control System led to some difficulty in pushing the code to the main repo and this took up some of my extra time.
- Yes.Took help from my mentors and some online resources.
- No.
- No.
- Work on setting up the conversation screen by inserting text from the database to the screens.
- Complete documentation of the work done so far, test functionalities and get code reviews
- Any further improvement in design after mentors' reviews and feedback.
- On schedule.
- Worked on documentation of the work done so far on my blog.
- Discussed with mentors and project managers about the requirements and certain issues for further development of the game.
- Submitted mid-term evaluation
- Learnt about animation in navigation, game development
- My mentor is unable to build the code pushed by me in the systers/PowerUp repo.
- No. We are still trying to figure out the problem. My mentor shall get back to me about what errors are being encountered while building the code and meanwhile I am rechecking my commits and PR.
- The problem with not building the pushed code still persists. I am coordinating with my mentor for the same and checking out online resources.
- Not as of now. If we are unable to solve it, I would ask for further assistance.
- Work on developing the conversation screens according to the scenarios provided by the project managers.
- Work on animations and the design of the game
- Documentation of work and commit code on GitHub.
- On schedule.
- Worked on integrating the new conversation sent by the Project Managers into the app.
- Made an alternate schema of the database so that a single csv file of a scenario can be easily imported into the database.
- Had a meeting with the mentors,Project Managers on Google Hangout where work was discussed and some observations/feedback was obtained.
- The code pushed on GitHub of the work done so far fails to build due to the path of certain files not having been set correctly.
- No. I have been communicating with my mentors for the past week about the same and I am trying to get rid of the errors being displayed while building.
- The problem with not building the pushed code still persists. I have got a few suggestions from mentors on Github conversations about the same and I am exploring those solutions and trying to get rid of the errors.
- Not as of now. If we are unable to solve it, I would ask for further assistance.
- Work on the replay button after the completion of a scenario
- Getting the new scenario into the database and the app
- Work on other finer points like giving points for each answer and displaying the score only after the completion of scenario.
- On schedule till the mid-term evaluation schedule. Need to draft a new timeline for the latter part of the program.
- The new scenario (on friendship and choices) has been integrated in the app according to a new database schema to make it compatible with the given csv file
- Added the replay button which allows user to play the scenario again
- Made active links for the logo button that allows user to go back to the start screen
- Made changes in the path of certain files to resolve last week's errors. The code from GitHub is now building.
- There are some issues with uploading data from database to the app with the simulator.
- The data from the database can be fetched on local machines but DB path has to be set manually for each simulator that the user is using. It would be better if we could find a way to fetch that data without having to set the path manually for each simulator.
- I am going through some online resources to fix the above problem. There are similar questions put up on StackOverFlow and there seems to be no immediate solution to this problem. I shall talk to my mentors and do further research on the same
- Not as of now. If we are unable to solve it, I would ask for further assistance.
- Implement some animations for the conversation screens of the current scenario that I am working with.
- Update points for each answer in the conversation and display the total score at the end.
- Update documentation of the work done so far, push the code on GitHub for code review.
- On schedule as per the timeline- post mid term submitted to mentors and PMs.
- The Scenario (on friendship and choices) is now running in the app with appropriate decision making mechanism
- Added the replay and map screen button which would pop up after the completion of that scenario
- Implemented a few animation techniques for displaying text and hiding buttons/images as per the requirement of the app
- Working on an alternate csv file/database schema for a smooth import of csv files into our database
- The problem of not being able to automatically fetch data from the database still exists; need to set the path for the database file in the individual simulator
- No. I did speak to my mentors about it and they faced the same issue. I hope to bring up this issue in the Bi-Weekly meeting with all mentors and PMs.
- I am still trying to figure out the potential solution for the above problem because the code seems unlikely to merge unless we can get it working for each simulator without having to set the path.
- I hope to bring up the issue in the Bi-Weekly Meeting with the Project Managers and other people working on iOS apps.
- Start Work on initial Avatar Creation Screen.
- Make further amends in the csv file format and the database schema which would be easy to work with
- Complete at leat 1 conversation scenario after having received mock-ups and images.
- Documentation and testing functionalities
- On schedule as per the timeline- post mid term submitted to mentors and PMs.
- Finally resolved the error that was encountered while fetching data from the database file when the app is run on the simulator. This was accomplished with further deeper research on the main problem.
- Pushed my code on GitHub, waiting for mentor approval and review so that it can be merged.
- Worked on a new screen for the scenarios from the images and mock-ups provided by mentors this week.
- Worked on certain aspects of the Avatar creation screen, have some doubts that I hope to clarify in the meeting today with mentors and PMs.
- No
- N.A.
- Some doubts about the database schema and csv file, avatar creation screen and other details about the app in general are there which would be clarified in the meeting today.
- No
- Work on the Avatar creation screen further with the images and mock-ups.
- Add some features and functionalities in this screen after discussion with mentors and PMs about the same.
- Get code review and feedback and work on code cleaning.
- On schedule
- Updated the team about my work done so far in the meeting
- Made some changes in code pushed on GitHub by making text-fields non-editable.
- Added .gitignore file in the repo.
- Working on the Avatar creation screen set up.
- None
- N.A.
- Some points need to be discussed with the mentors and Project managers. I have sent a mail to the team so that we can iterate over those points and further developments can be made.
- No
- Get code review and feedback so that pull request can be merged.
- Further developments in the Avatar character screen and the features.
- After discussion with the team, make changes/modifications in DB design, orientation of the app, make additional screens for About Button and the second scenario
- On schedule
- Worked on the development of the second level scenario (Sex-Scenario). The conversations and decision making mechanism have been implemented.
- Integrated the images obtained from PMs into this scenario
- Fixed a few bugs in the repo, as suggested by mentors
- Tested the app and made modifications in UI.
- None
- N.A.
- Discussion about documentation, close out and additional questions and comments would happen happen in the Bi-Weekly Meeting today(Monday) at 1pm EST.
- No
- Get code review and feedback so that pull request can be merged.
- Additional features and animations to be included
- Code scrubbing, documentation, review
- On schedule
- Incorporated the images provided by PMs in the first scenario (communication and refusal skills) as discussed in the meeting last time.
- Modified the UI design for the first scenario and included the concluding text in the endscreen.
- Fixed a few bugs in the repo in the process of making the aforementioned changes
- Worked on the documentation
- None
- N.A.
- None
- No
- Code to be merged after final PR
- Push app to the store
- Final changes and modifications keeping in mind the final pencils down line i.e. 21st August
- Code scrubbing, final documentation and demo
- On schedule
- Final commits and code cleaning before the hard pencils down.
- Pushed the final commit on GitHub
- Final presentation/demo on PowerUp
- Completed the official documentation
- Submitted the final evaluation
- None
- N.A.
- None
- No
- N.A.
- On schedule